Apache HBase vs. Percona Server for MongoDB

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.

Incentivized

It offers good support for the implementation of solutions in the public and on-premises cloud and integration with other services such as Hashicorp Vault for data encryption. One of the main advantages is the ease of configuration, in addition to offering transaction support for the different operations and scalability of the servers.

Incentivized

• 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.

Incentivized

• High performance
• Integration with other tools and services
• Big data projects oriented
• High availability and scalability

Incentivized

• 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.

Incentivized

• The learning curve makes it a bit tricky to use at first.
• Documentation is an aspect to improve, especially for people who are just starting out.
• At the interface level, the user experience could be improved.

Incentivized

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.

Incentivized

One aspect to improve is the user experience since sometimes the steps to take are not clear and the user may need to review some of the actions before continuing with the next ones. Another aspect to improve is the documentation and support for developers who want to know the tool.

Incentivized

It offers good support for the implementation of solutions in the public and on-premises cloud and integration with other services such as Hashicorp Vault for data encryption. Also, it offers support for different compatible programming languages such as C, C ++, Java, as well as offering good support for the persistence of schema-free data and the possibility of saving data in memory.

Incentivized

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.

Incentivized

At the performance level, it is similar to other solutions such as MongoDB and Percona Server for MySQL. and at the customization level, it offers better support for the development of specific solutions that seek good performance in transactions.

Incentivized

• 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.

Incentivized

• It offers a good alternative solution compared with other open source databases.
• We have many resources at the documentation level and other tools that help the integration with different programming languages.

Incentivized