What users are saying about
Top Rated
29 Ratings
6 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8 out of 101
Top Rated
29 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 8.2 out of 101

Add comparison

Likelihood to Recommend

Aerospike Database

Compared to Redis and memcacheD, high availibity is best from Aerospike. Load balancing is also well done through Aerospike. If you're doing K/V lookups data exceeds more than 1MB, then Aerospike definitely fits the bill. However, it is not best as a document store. It is really atrocious in that nature. If anything look @ Mongo or something else then.
Anson Abraham profile photo

HBase

HBase is well suited for streaming ingest, fast lookups, massive datasets, data warehouse lookup tables, RDBMS replacement, MongoDB replacement, key-value store, data scans, logs, JSON storage and some binary storage.My preferred use case is for storing data points like time series or data produced by sensors. I often use HBase when I need data available immediately and I am not looking for transactions. This is a great store for really wide tables with tons of columns. It is also great if you are not sure what type of data you are going to have. It really excels at sparse data.
Timothy Spann profile photo

Feature Rating Comparison

NoSQL Databases

Aerospike Database
HBase
8.0
Performance
Aerospike Database
HBase
7.8
Availability
Aerospike Database
HBase
8.0
Concurrency
Aerospike Database
HBase
7.3
Security
Aerospike Database
HBase
7.8
Scalability
Aerospike Database
HBase
8.2
Data model flexibility
Aerospike Database
HBase
8.4
Deployment model flexibility
Aerospike Database
HBase
8.8

Pros

  • Scales really quickly and easily. Can deploy a new cluster or add to a cluster fairly quick.
  • MGMT UI is easy to use. Utilizing cli, makes it easy to "autoscale" for us.
  • The sharding removes any need to overlook to make sure if balanced correctly.
  • HA is dead simple, that almost little to no need figure out how to do it.
Anson Abraham profile photo
  • 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

  • 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 profile photo
  • Not for small data
  • Requires a cluster
Timothy Spann profile photo

Likelihood to Renew

Aerospike Database8.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 profile photo
HBase8.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

Compared to the above for K/V lookups and writes, it is faster. However, less than 1 MB, i'd use Redis, if you're willing to write package for HA in Redis. However HA between Redis and aerospike, aerospike is top notch. K/V lookups were 20-30% faster than Redis, 50% faster than Mongo, and 45% faster than Cassandra. But again, aerospike is really expensive.
Anson Abraham profile photo
Typically, Cassandra is faster on reads and HBase is faster on writes. You use Cassandra when you want to use a website, HBase is just an overall good general use database engine. Cassandra has its own storage engine and HBase uses HDFS and all its benefits. MongoDB is typically also used in web development, it has a great support for JSON but it's been known for poor scalability. It also uses its own storage engine.
No photo available

Return on Investment

  • Less mgmt headaches, prompting time to focus on other issues.
  • HA, required little handholding. And minimization of downtime.
  • Cross region replication is not great, which sometimes requires data integrity checks on your end.
Anson Abraham profile photo
  • We were able to scale our application from 5TB running in a relational database to 20TB on top of HBase
  • Application availability was always high even with half of the nodes having hardware issues
  • HBase can be used with standard mechanical harddrive storage. There's no need for fancy SAN or NAS storage with HBase which is almost always expensive.
No photo available

Pricing Details

Aerospike Database

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

HBase

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