Azure Cosmos DB vs HBase: What are the differences?
Developers describe Azure Cosmos DB as "A fully-managed, globally distributed NoSQL database service". Azure DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development. On the other hand, HBase is detailed as "The Hadoop database, a distributed, scalable, big data store". Apache HBase is an open-source, distributed, versioned, column-oriented store modeled after Google' Bigtable: A Distributed Storage System for Structured Data by Chang et al. Just as Bigtable leverages the distributed data storage provided by the Google File System, HBase provides Bigtable-like capabilities on top of Apache Hadoop.
Azure Cosmos DB belongs to "NoSQL Database as a Service" category of the tech stack, while HBase can be primarily classified under "Databases".
"Best-of-breed NoSQL features" is the top reason why over 13 developers like Azure Cosmos DB, while over 7 developers mention "Performance" as the leading cause for choosing HBase.
HBase is an open source tool with 2.91K GitHub stars and 2.01K GitHub forks. Here's a link to HBase's open source repository on GitHub.
According to the StackShare community, HBase has a broader approval, being mentioned in 54 company stacks & 18 developers stacks; compared to Azure Cosmos DB, which is listed in 24 company stacks and 24 developer stacks.
What is Azure Cosmos DB?
What is HBase?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using HBase?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The final output is inserted into HBase to serve the experiment dashboard. We also load the output data to Redshift for ad-hoc analysis. For real-time experiment data processing, we use Storm to tail Kafka and process data in real-time and insert metrics into MySQL, so we could identify group allocation problems and send out real-time alerts and metrics.
If you need a document-based database with geo-redundancy (imagine AU-HU distance), this is the way to go.