Aerospike vs. Apache HBase

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.

Incentivized

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.

Incentivized

• featured with robustness and reliability
• low hardware resource consumption especially RAM
• open-source
• distributed no-sql server

Incentivized

• Scalable and truly non-relational data
• HBase operations run in real-time on its database rather than MapReduce jobs
• Scales linearly to support billions of rows with millions of columns

Incentivized

• AQL is pretty limited and not as useful as the java client
• Documentation can be lacking for some products
• replication configuration is complicated

Incentivized

• Write performance
• Performance support for parquet file format. supports, but performance wise still not there
• API / library availability for spark, rather than creating a new library for it

Incentivized

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.

Incentivized

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.

Incentivized

Could be easier to use and install. Also developer experience needs some work

We used the community edition.

Incentivized

Aerospike is much more performant than MongoDB, however there is much greater community adoption and support for mongo

Incentivized

Compared NoSQL databases with traditional databases for faster retrieval and consistency. As MongoDB is a NoSQL supports dynamic fields, however, query performance is bad for aggregations and added maintenance. When compared with MySQL and Teradata, it could not scale up as fast as Hbase and added cost involved to it. HBase can be easily scalable to a huge volume of records, have a faster lookup and provides consistency

Incentivized

• Being able to power the same workload on a fraction of the servers has led to better ROI for my application.
• Less servers needed also meant less time to manage the cluster, leading to savings in engineering time

• Positive: Open source, easy to use, good to store big data.
• Negative: SQL functionalities are not available.
• More memory utilization
• More troubleshooting

Incentivized