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.

Comments

Popular posts from this blog

In-memory data model with Apache Gora

Open source in-memory data model and persistence for big data framework Apache Gora™ version 0.3, was released in May 2013. The 0.3 release offers significant improvements and changes to a number of modules including a number of bug fixes. However, what may be of significant interest to the DynamoDB community will be the addition of a gora-dynamodb datastore for mapping and persisting objects to Amazon's DynamoDB. Additionally the release includes various improvements to the gora-core and gora-cassandra modules as well as a new Web Services API implementation which enables users to extend Gora to any cloud storage platform of their choice. This 2-part post provides commentary on all of the above and a whole lot more, expanding to cover where Gora fits in within the NoSQL and Big Data space, the development challenges and features which have been baked into Gora 0.3 and finally what we have on the road map for the 0.4 development drive.
Introducing Apache Gora Although there are var…

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…

Amazon DynamoDB datastore for Gora

What was initially suggested during causal conversation at ApacheCon2011 in November 2011 as a “neat idea”, would soon become prime ground for Gora's first taste of participation within Google's Summer of Code program. Initially, the project, titled Amazon DynamoDB datastore for Gora, merely aimed to extend the Gora framework to Amazon DynamoDB. However, it seem became obvious that the issue would include much more than that simple vision.

The Gora 0.3 Toolbox We briefly digress to discuss some other noticeable additions to Gora in 0.3, namely: Modification of the Query interface: The Query interface was amended from Query<K, T> to Query<K, T extends Persistent> to be more precise and explicit for developers. Consequently all implementors and users of the Query interface can only pass object's of Persistent type. Logging improvements for data store mappings: A key aspect of using Gora well is the establishment and accurate definitio…