TrustRadius
HBase as the brother of big data
https://www.trustradius.com/nosql-databasesHBaseUnspecified8.230101
RAVI MISHRA profile photo
March 16, 2019

HBase as the brother of big data

Score 7 out of 101
Vetted Review
Verified User
Review Source

Overall Satisfaction with HBase

I use HBase because it is a NoSQL database and it is open sourced and can store big data. We can store any structured, semi-structured and unstructured data easily. One other major benefit is, it is a columnar database so no need to specify any schema. I generally use it when I store the streaming data, the analysis is also faster after connecting the HBase with Spark. HBase is a mature database so we can connect HBase with various execution engine and other component using JDBC.
  • HBase stores the big data in a great manner and it is horizontally scalable.
  • Another major reason is security, we can secure the HBase database using Atlas, Ranger.
  • Store any format of data like structured, semi-structured and unstructured.
  • Consistency
  • Strongly consistent reads and writes are provided by HBase, we use it for high-speed requirements if we do not need RDBMS-supported features such as full transaction support or typed columns.
  • There are very few commands in HBase.
  • Stored procedures functionality is not available so it should be implemented.
  • HBase is CPU and Memory intensive with large sequential input or output access while as Map Reduce jobs are primarily input or output bound with fixed memory. HBase integrated with Map-reduce jobs will result in random latencies.
  • Positive: Open source, easy to use, good to store big data.
  • Negative: SQL functionalities are not available.
  • More memory utilization
  • More troubleshooting
HBase is more secure. Easily scalable. HBase is for wide-column store while MongoDB is for document store. Triggers available in HBase while in Mongodb triggers are not available.
HBase is open source so I suggest it and it is one of the best databases to store real-time data with security but a lot more improvements are required to include the SQL queries functionalities for the data analysis purpose.
While we have a variable schema with slightly different rows and when you are going for a key dependent access to our stored data, we prefer to use HBase. No requirement of relational features. If we do not need features like transaction, triggers, complex query, complex joins etc. then go for HBase.

HBase Feature Ratings

Performance
7
Availability
8
Concurrency
8
Security
8
Scalability
9
Data model flexibility
6
Deployment model flexibility
8