What users are saying about
11 Ratings
32 Ratings
11 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.2 out of 100
32 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 7.4 out of 100

Feature Set Ratings

  • Aerospike ranks higher in 1 feature set: NoSQL Databases

NoSQL Databases

8.9

Aerospike

89%
7.7

HBase

77%
Aerospike ranks higher in 6/7 features

Performance

9.6
96%
2 Ratings
7.1
71%
5 Ratings

Availability

8.4
84%
2 Ratings
7.8
78%
5 Ratings

Concurrency

9.4
94%
2 Ratings
7.0
70%
5 Ratings

Security

9.0
90%
1 Rating
7.8
78%
5 Ratings

Scalability

8.7
87%
2 Ratings
8.6
86%
5 Ratings

Data model flexibility

9.1
91%
2 Ratings
7.1
71%
5 Ratings

Deployment model flexibility

8.0
80%
2 Ratings
8.2
82%
5 Ratings

Attribute Ratings

  • Aerospike is rated higher in 1 area: Likelihood to Renew
  • Apache HBase is rated higher in 1 area: Likelihood to Recommend

Likelihood to Recommend

7.6

Aerospike

76%
3 Ratings
7.7

HBase

77%
10 Ratings

Likelihood to Renew

8.0

Aerospike

80%
1 Rating
7.9

HBase

79%
10 Ratings

Usability

8.7

Aerospike

87%
2 Ratings

HBase

N/A
0 Ratings

Support Rating

8.6

Aerospike

86%
2 Ratings

HBase

N/A
0 Ratings

Likelihood to Recommend

Aerospike

We were developing an advertisement time auction application, where we had to store the client's personal details, advertisement-related details, location, and many other details. Moreover, we required a promotion, cookies, and a few more details from the front end. All this information is heavy in terms of size and cannot be lost if the server crash. So, we required an extremely fast disk database with high scalability and low throughput.
Savan Solanki | 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

Pros

Aerospike

  • Low latency
  • Stable
  • Highly configurable
  • increasing features
Anonymous | 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

Aerospike

  • Load balancing per network segments.
  • Reduction in price.
  • Cross datacenter replication usage isn't so straightforward. Sometimes cross dc replication can have issues of bad data..
Anson Abraham | 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

Pricing Details

Aerospike

General

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

Starting Price

HBase

General

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

Starting Price

Likelihood to Renew

Aerospike

Aerospike 8.0
Based on 1 answer
If money isn't an issue, and you're not on the cloud, then I'd go with Aerospike. If you're the cloud ie, aws or azure, then i'd stick with dynamoDB or Cosmos then. Aerospike is definitely not something you want to put into the cloud. It doesn't work well w/ cross regions. If cross DC, you'll have to write some stuff for data integrity checks.
Anson Abraham | 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

Usability

Aerospike

Aerospike 8.7
Based on 2 answers
We were in dilemma in deciding the database and it was the first time we were using Aerospike. Eventually, everything went as expected and resolved the client's requirement along with positive feedback and appreciation
Savan Solanki | TrustRadius Reviewer

HBase

No score
No answers yet
No answers on this topic

Support Rating

Aerospike

Aerospike 8.6
Based on 2 answers
You pay for the level of support.
Anonymous | TrustRadius Reviewer

HBase

No score
No answers yet
No answers on this topic

Alternatives Considered

Aerospike

Aerospike is much more performant than MongoDB, however there is much greater community adoption and support for mongo
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

Aerospike

  • increased response time
  • minimal managerial resource required
  • developer can start using with shallow learning curve
Savan Solanki | 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

Add comparison