What users are saying about
17 Ratings
30 Ratings
17 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.1 out of 100
30 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 7.9 out of 100

Likelihood to Recommend

Azure Cosmos DB

If you need to store high volumes/velocity of unstructured data, Azure Cosmos DB definitely worth looking at.
Anonymous | TrustRadius Reviewer

HBase

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.
Vinaybabu Raghunandha Naidu | TrustRadius Reviewer

Feature Rating Comparison

NoSQL Databases

Azure Cosmos DB
7.9
HBase
7.7
Performance
Azure Cosmos DB
8.4
HBase
7.1
Availability
Azure Cosmos DB
8.8
HBase
7.8
Concurrency
Azure Cosmos DB
7.3
HBase
6.8
Security
Azure Cosmos DB
7.0
HBase
7.7
Scalability
Azure Cosmos DB
9.1
HBase
8.4
Data model flexibility
Azure Cosmos DB
7.3
HBase
7.5
Deployment model flexibility
Azure Cosmos DB
7.4
HBase
8.3

Pros

Azure Cosmos DB

  • Turn-key geo-redundancy with multi-master writes is unprecedented and unparalleled in the industry!
  • Guaranteed low latency makes Cosmos DB an excellent fit for most of our performance-intensive situations.
  • The tunable consistency model simplifies so many challenges in distributed systems engineering that otherwise require advanced knowledge of computer science topics. I continue to be impressed at how Cosmos DB has abstracted away so much complexity.
Lars Kemmann | TrustRadius Reviewer

HBase

  • 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.
Timothy Spann | TrustRadius Reviewer

Cons

Azure Cosmos DB

  • ANSI SQL support
  • Pure ACIDity support
Anonymous | TrustRadius Reviewer

HBase

  • 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.
RAVI MISHRA | TrustRadius Reviewer

Likelihood to Renew

Azure Cosmos DB

Azure Cosmos DB 8.2
Based on 4 answers
Excellent Customer Service which is the key thing from Microsoft. Another big advantage is their documentation and tech support and meeting industry standards.
Anonymous | TrustRadius Reviewer

HBase

HBase 8.1
Based on 10 answers
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.
Anonymous | TrustRadius Reviewer

Alternatives Considered

Azure Cosmos DB

Our development and administration teams are just more familiar with the Microsoft Stack, and there was very little additional knowledge required to put this into production.
Anonymous | TrustRadius Reviewer

HBase

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.
Anson Abraham | TrustRadius Reviewer

Return on Investment

Azure Cosmos DB

  • Tremendously reduced our time-to-market with solutions built on graph databases
  • Helped our team to think more broadly about data by making NoSQL options much more accessible
  • Saved us significant effort on geo-replication and global availability
Lars Kemmann | TrustRadius Reviewer

HBase

  • 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.
Bharadwaj (Brad) Chivukula | TrustRadius Reviewer

Pricing Details

Azure Cosmos DB

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

HBase

General

Free Trial
Free/Freemium Version
Premium Consulting/Integration Services
Entry-level set up fee?
No

Rating Summary

Likelihood to Recommend

Azure Cosmos DB
7.3
HBase
7.9

Likelihood to Renew

Azure Cosmos DB
8.2
HBase
8.1

Add comparison