Likelihood to Recommend Hbase is well suited for large organizations with millions of operations performing on tables, real-time lookup of records in a table, range queries, random reads and writes and online analytics operations. Hbase cannot be replaced for traditional databases as it cannot support all the features, CPU and memory intensive. Observed increased latency when using with MapReduce job joins.
Read full review We have built a database of a network of bank branches with all the needs of security and recovery/restart. It requires knowledge of obsolete maintenance languages and perhaps it is too rigid in the schemes.
Read full review Pros Scalability. HBase can scale to trillions of records. Fast. HBase is extremely fast to scan values or retrieve individual records by key. HBase can be accessed by standard SQL via Apache Phoenix. Integrated. I can easily store and retrieve data from HBase using Apache Spark. It is easy to set up DR and backups. Ingest. It is easy to ingest data into HBase via shell, Java, Apache NiFi, Storm, Spark, Flink, Python and other means. Read full review Security Reliability Big volume of data and good performance Read full review Cons 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. Read full review Certainly, not being a DB relational penalizes its use It should be more flexible Open up to more recent languages Read full review Likelihood to Renew There's really not anything else out there that I've seen comparable for my use cases. HBase has never proven me wrong. Some companies align their whole business on HBase and are moving all of their infrastructure from other database engines to HBase. It's also open source and has a very collaborative community.
Read full review Alternatives Considered Cassandra os great for writes. But with large datasets, depending, not as great as HBASE.
Cassandra does support parquet now. HBase still performance issues.
Cassandra has use cases of being used as time series. HBase, it fails miserably. GeoSpatial data, Hbase does work to an extent. HA between the two are almost the same.
Read full review Essentially, for a question of reliability and scalability, the performance has always been of an enterprise level. The utilities are efficient and effective.
Read full review 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. Read full review The investment made about 20 years ago that has been fully repaid Reliability and security of investments Unfortunately, it is quite outdated and therefore maintenance costs are higher because the skills are not always available. Read full review ScreenShots