Item: Apache HBase
Rating: 9
Author: Bharadwaj (Brad) Chivukula

Overall Satisfaction with HBase

Use Cases and Deployment Scope

HBase was used as a datastore for the retails product catalog and session maangement

Pros and Cons

Pros

Scalable and truly non-relational data
HBase operations run in real-time on its database rather than MapReduce jobs
Scales linearly to support billions of rows with millions of columns

Cons

Difficult for people who are building custom tools for SQL like purposes to understand HBase
Cannot be used for transactional datasets

Return on Investment

As Hbase is a noSql database, here we don't have transaction support and we cannot do many operations on the data.
Not having the feature of primary or a composite primary key is an issue as the architecture to be defined cannot be the same legacy type. Also the transaction concept is not applicable here.
The way data is printed on console is not so user-friendly. So we had to use some abstraction over HBase (eg apache phoenix) which means there is one new component to handle.

Alternatives Considered

Cassandra and MongoDB

Hbase is more robust and scalable than other DBs around

Likelihood to Renew

HBase is in the right direction when it comes to NoSQL DB.

Suited for storing bulk data in a tabular manner, I would recommend Hadoop HBase, but for a small amount of data, I personally would not suggest the use of this tool. We are moving from a traditional file system to a Hadoop file system, and to store the data in a tabular manner, we are using HBase. As the data is increasing day by day, the need to manage the same is also required, which is incorporated by Hadoop.

HBase Feature Ratings

Comments

Please log in to join the conversation

An Amazing Experience