Skip to main content

Pricing models for Hadoop products

A look at the various pricing models adopted by the vendors in the Hadoop ecosystem. While the pricing models are evolving in this rapid and dynamic market, listed below are some of the major variations utilized by companies in the sphere.

1) Per Node:

Among the most common model, the node based pricing mechanism utilizes customized rules for determining pricing per node. This may be as straight forward as pricing per name node and data node or could have complex variants of pricing based on number of core processors utilized by the nodes in the cluster or per user license in case of applications.

2) Per TB:

The data based pricing mechanism charges customer for license cost per TB of data. This model usually accounts non replicated data for computation of cost.

3) Subscription Support cost only:

In this model, the vendor prefers to give away software for free but charges the customer for subscription support on a specified number of nodes. The support timings and level of support further determine the subscription cost.

4) Package deal - Hardware, Software and services

Besides commodity hardware, the vendors have built specialized hardware and appliances which leverage Hadoop to the maximum. Pricing deals are worked out involving a combination of hardware, software and services for the deployment and maintenance.

5) Freemium:

The freemium model attracts the customer with free usage till a threshold limit. The limit, for example, may be in terms of data per day or number of user licenses or number of nodes. Beyond the threshold, the customer is charged on specified rates.

6) Connector costs:

As current systems have started integrating with HDFS, the vendors are also trying to make some money by selling specialized connectors. In some cases, the number of connectors is limited for free usage with paid subscription for broader number of connectors.

7) Cloud:

Within the cloud deployment, two models are more commonly popular:
- Pay-per-use: which imply cost based on usage charged periodically to credit or billing account.
- Half yearly or annual subscription: which imply special package for longer duration subscription commitment.
Further, the cloud models utilize charging models as a combination of one or more factors:
* Per node cost
* MapReduce cost
* Software usage per hour
* Storage cost
* Data Transfer cost
* Processing cost

During the year 2014, we expect higher pressure on licensing model while freemium models or pay per use models to take further flight. There will be downward pricing pressure on all vendors which could impact their margins and interest in the commoditized products. More interest will eventually grow towards specialized applications and services for customer which could lead to higher profit margins.


Popular posts from this blog

Data deduplication tactics with HDFS and MapReduce

As the amount of data continues to grow exponentially, there has been increased focus on stored data reduction methods. Data compression, single instance store and data deduplication are among the common techniques employed for stored data reduction.
Deduplication often refers to elimination of redundant subfiles (also known as chunks, blocks, or extents). Unlike compression, data is not changed and eliminates storage capacity for identical data. Data deduplication offers significant advantage in terms of reduction in storage, network bandwidth and promises increased scalability.
From a simplistic use case perspective, we can see application in removing duplicates in Call Detail Record (CDR) for a Telecom carrier. Similarly, we may apply the technique to optimize on network traffic carrying the same data packets.
Some of the common methods for data deduplication in storage architecture include hashing, binary comparison and delta differencing. In this post, we focus on how MapReduce and…

Low latency SQL querying on HBase

HBase has emerged as one of the most popular NoSQL database offering distributed, versioned, non-relational tables hosted on commodity hardware. However, with a large set of users coming from a relational SQL world, it made sense to bring the SQL back in this NoSQL. With Apache Phoenix, database professionals get a convenient way to query HBase through SQL in a fast and efficient manner. Continuing our discussion with James Taylor, the founder of Apache Phoenix, we focus on the functional aspects of Phoenix in this second part of interaction.
Although Apache Phoenix started off with distinct low latency advantage, have the other options like Hive/Impala (integrated with HBase) caught up in terms of performance?
No, these other tools such as Hive and Impala have not invested in improving performance against HBase data, so if anything, Phoenix's advantage has only gotten bigger as our performance improves.  See this link for comparison of Apache Phoenix with Apache Hive and Cloudera Im…