Aerospike Database
AerospikeExternal reviews
69 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Aerospike the nosql key-value database on steroids
What do you like best about the product?
I've tested Aerospike [1] and other nosql databases when we were looking for a viable alternative to what we had as we were reaching its limit. What I liked in Aerospike is that you can easily confirm the exactitude of the performance claims, which is not the case for most commercial products. Also, in contrast to usual databases, there is no need to define sharding (i.e. how data will be fragmented on the different nodes of the database) or replication parameter (i.e. the number of node on which your data will be replicated so that you don't loose anything in case of node failure). These parameters are essential but as a developer you don't have to care much about them as Aerospike will do.
Also, Aerospike gives you the choice between in-memory storage (e.g. to cache user session data) or SSD disk storage (for durability) without any compromise in performance.
It has a powerful query language, and enable users to define custom aggregation functions based on the Lua programming language [2] which is very flexible especially when it comes to define business related aggregation algorithms.
Above all that, it is an Open Source solution.
[1] https://github.com/dzlab/analytics-examples/blob/master/nosql-batch-examples/src/main/scala/aerospike/java_sdk.scala
[2] https://github.com/dzlab/analytics-examples/blob/master/nosql-batch-examples/src/main/resources/udf/aggregations.lua
Also, Aerospike gives you the choice between in-memory storage (e.g. to cache user session data) or SSD disk storage (for durability) without any compromise in performance.
It has a powerful query language, and enable users to define custom aggregation functions based on the Lua programming language [2] which is very flexible especially when it comes to define business related aggregation algorithms.
Above all that, it is an Open Source solution.
[1] https://github.com/dzlab/analytics-examples/blob/master/nosql-batch-examples/src/main/scala/aerospike/java_sdk.scala
[2] https://github.com/dzlab/analytics-examples/blob/master/nosql-batch-examples/src/main/resources/udf/aggregations.lua
What do you dislike about the product?
We really liked Aerospike, but as our use case was about Aanalytics that needs running heavy read-only analysis workload on the database. In addition, our use case required one big write workload directly from Apache Spark RDDs (Resilient Distributed Dataset) that may consists of billions of rows and hundreds of properties. These use cases were sadly not the appropriate cases where Aerospike can be used as it's a key-value database and not columnar oriented.
What problems is the product solving and how is that benefiting you?
We evaluated Aerospike among other nosql solutions for Analytics workload and we found that it didn't fit well with our requirements. But we realized how good it is when it comes to caching volatile data.
Recommendations to others considering the product:
If what you need is a very low-latency access to single data, then you must consider trying Aerospike. If you are on AWS and look for an easily deployable key-value store, then you have to consider Aerospike as it has an officile AMI (Amazon Machine Images) that you can use directly from the marketplace. In contrast, if you're looking for a nosql solution to use as backend for you analytic workloads then Aerospike may not be the appropriate solution, but you can still evaluate it as this may evolve over time.
showing 71 - 71