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

Likelihood to Recommend

Azure Cosmos DB

Cosmos DB is hands-down the most flexible and performant way to store and access data related to the functionality of your applications. If you don't really need a 3rd-normal-form relational schema, and if you're not working on a (hot or cold) big data analytics scenario, then you should almost definitely be using Cosmos DB! The only major exception is if your use case can be addressed with some thoughtful planning and use of plain old Azure Storage, which might not get a lot of attention but is still a rock-solid platform.
Lars Kemmann profile photo

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 profile photo

Feature Rating Comparison

NoSQL Databases

Azure Cosmos DB
9.6
HBase
7.9
Performance
Azure Cosmos DB
9.0
HBase
7.5
Availability
Azure Cosmos DB
10.0
HBase
7.9
Concurrency
Azure Cosmos DB
10.0
HBase
7.0
Security
Azure Cosmos DB
10.0
HBase
7.7
Scalability
Azure Cosmos DB
10.0
HBase
8.2
Data model flexibility
Azure Cosmos DB
10.0
HBase
8.1
Deployment model flexibility
Azure Cosmos DB
8.0
HBase
8.6

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 profile photo

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 profile photo

Cons

Azure Cosmos DB

  • Cosmos DB can be very expensive if you're using it for scenarios that are better completed in regular old Azure Table Storage or Blob Storage, specifically if you put some thought into your partitioning schemes. No product is a good substitute for thoughtful system design.
  • It would be helpful if I had some more insight into how many resources (DTUs) an individual query uses.
  • The auto-indexing is great, but a little mysterious -- not usually an issue but it does require some intentional thought.
Lars Kemmann profile photo

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 profile photo

Likelihood to Renew

Azure Cosmos DB

Azure Cosmos DB 10.0
Based on 1 answer
Cosmos DB has such a head start and unique position in the market, backed as it is by Microsoft's global backbone network, that it's hard to imagine any other solution coming close to it in terms of overall capabilities. While it's not the right fit for every situation, whenever Cosmos DB is a candidate it should probably be your first choice.
Lars Kemmann profile photo

HBase

HBase 8.3
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.
No photo available

Alternatives Considered

Azure Cosmos DB

Cosmos DB is unique in the industry as a true multi-model, cloud-native database engine that comes with solutions for geo-redundancy, multi-master writes, (globally!) low latency, and cost-effective hosting built in. I've yet to see anything else that even comes close to the power that Cosmos DB packs into its solution. The simplicity and tooling support are nice bonus features as well.
Lars Kemmann profile photo

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 profile photo

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 profile photo

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 profile photo

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

Add comparison