What users are saying about
Top Rated
102 Ratings
31 Ratings
Top Rated
102 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 8.5 out of 100
31 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

Amazon DynamoDB

It is ideal for those projects where you need to store a large amount of data, but you do not know how many will be so you need the database to increase its storage capacity together with the number of users, without having to spend extra money, it also has a great potential thanks to the fast connection it offers, so the data travels at high speed, and this speeds up the performance of the applications, excellent for projects where non-relational databases are used and what matters is to store large quantities of information and use them at high speed.
Winston Mendes | 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

Amazon DynamoDB
8.5
HBase
7.7
Performance
Amazon DynamoDB
8.7
HBase
7.1
Availability
Amazon DynamoDB
9.3
HBase
7.8
Concurrency
Amazon DynamoDB
8.7
HBase
7.0
Security
Amazon DynamoDB
9.0
HBase
7.8
Scalability
Amazon DynamoDB
8.9
HBase
8.5
Data model flexibility
Amazon DynamoDB
7.1
HBase
7.2
Deployment model flexibility
Amazon DynamoDB
8.1
HBase
8.3

Pros

Amazon DynamoDB

  • It's very easy to get started, creating a table with a partition/sort key and you're on your way.
  • You can scale up and down your read/write IO as needed.
  • You can store structured and unstructured data.
  • It works great with Web Development as it's JSON based.
Bob Smith | 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

Amazon DynamoDB

  • Complex searching (no support for case-insensitive or full-text search).
  • Only supports up to two-key indexes.
  • Requires choosing the indexes up-front when doing searches.
  • Does not have an SQL compatible query front-end.
  • No join-table support (requires putting all data into one table).
Chris Moyer | 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

Amazon DynamoDB

Amazon DynamoDB 8.7
Based on 34 answers
We will most likely continue to use DynamoDB for certain use-cases. If we stopped using DynamoDB as often, it would likely be because we started using Aurora Serverless more. Aurora Serverless may offer similar availability, management and cost benefits while allowing developers to use their MySQL tools and experience.
Anonymous | TrustRadius Reviewer

HBase

HBase 7.9
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

Amazon DynamoDB

We evaluated using MongoDB or Amazon DyanmoDB. For us, the biggest advantage is that there's no maintenance cost for Amazon DynamoDB. Mongo gets complicated when you setup sharding. With Amazon DynamoDB, it's literally a push of button to increase throughput. This saves time and money on DevOps resources.
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

Amazon DynamoDB

  • Since the Amazon manages the instance, the amount of time a developer needs to spend configuring the database is less. For comparison, if we were to manage the same instance manually, we need to set up EC2 instance, install the DB, setup backup scripts, track backup failures, which is a great overhead for the dev. Using DynamoDB this overhead is reduced and hence having a great ROI.
  • Great documentation and easy setup makes an easy learning curve to transition to DynamoDB. Only caveat is as with any database, the data structure should be thoroughly analyzed for types of querying because there are limitations with the DynamoDB API.
  • Ties very well with rest of the Amazon eco system. Having rest of the applications in Amazon allows managing the application security a breeze.
Anudeep Palanki | 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

Screenshots

HBase

Pricing Details

Amazon DynamoDB

General

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

Amazon DynamoDB Editions & Modules

Edition
On-Demand - Write Operation$1.251
On-Demand Read Operation$0.251
On-Demand Data Stored$0.252
On-Demand Point-in-Time Recovery$0.202
On-Demand Snapshot$0.102
On-Demand Restoring a Backup$0.153
On-Demand Global Tables$1.8754
On-Demand Streams$0.025
On-Demand Data Requests Outside AWS Regions$0.096
Provisioned - Write Operation$0.000657
Provisioned - Read Operation$0.000137
Provisioned - Data Stored$0.258
Provisioned - Point-in-Time Recovery$0.208
Provisioned - Snapshot$0.108
Provisioned - Restoring a Backup$0.159
Provisioned - Global Tables$0.00097510
Provisioned - Streams$0.0211
Provisioned - Data Requests Outside AWS Regions$0.0912
  1. per million requests
  2. per GB per month
  3. per GB
  4. per million write operations replicated
  5. per 100,000 read operations
  6. per GB
  7. capacity unit per hour
  8. per GB per month
  9. per GB
  10. per Read Capacity
  11. per 100,000 read operations
  12. per GB
Additional Pricing Details

HBase

General

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

HBase Editions & Modules

Additional Pricing Details

Rating Summary

Likelihood to Recommend

Amazon DynamoDB
8.8
HBase
7.7

Likelihood to Renew

Amazon DynamoDB
8.7
HBase
7.9

Add comparison