Aerospike Reviews & Product Details

Easy to setup . easy lookups based on keys . Its much faster Review collected by and hosted on G2.com.

I dont have anything that i disliked in it. Review collected by and hosted on G2.com.

Aerospike is easily configured. One simple config file (which must be the same across all nodes in the cluster) takes care of it. System recovers well on its own when a node fails. The AMC is a nice GUI with good at-a-glance info about the cluster. The Enterprise version is especially nice because it allows you to query and set parameters without having to use the command line tools. The support is also great, and the logging is fun (messages like "Now there will be cake" when the node is up and ready to ingest info, and "Now there is icing" when XDR is functioning. Review collected by and hosted on G2.com.

Some of the tools aren't very easily interpreted or easy to use. The syntax can be confusing, and at one point there seemed to be a gang of tools that did similar things so it was confusing to know which one to use for what purpose.

Another issue I had was when I wanted to see some information about the kind of data we were storing, so I wanted to get a couple of rows so I can see what bins were being used, types, etc. I didn't want to select *everything* in a huge database, but there is no option to limit the output as there is with say, HBase. You have to use an external tool to do that. Also wish there was a way to do something SQL-like in terms of describing a row or set.

Lastly, I wish there was a way to have different TTLs for different clusters. For example, if you have a main cluster that you need to retain data in for a longer period of time for compliance, but in a remote cluster you don't need the same requirements, it can cause a waste of resources and become expensive. Since XDR sees shipped logs as client writes, maybe there should be a separate setting for XDR ttls. gmail Review collected by and hosted on G2.com.

Unlike other NoSql products (... cassandra hint...) Aerospike is very easy to set up and does not have weird, unexpected behavior. UDF's are fairly difficult to write and debug, but if you have a few simple ones they are very valuable. The Java Client for Aerospike is very good. Review collected by and hosted on G2.com.

Indices and scans are fairly rudimentary. Unless your use case is purely a key-value store with a one-to-one mapping, this probably isn't the right database for you. Review collected by and hosted on G2.com.

Simplicity of the architecture. Ease of Operations. high concurrency,low latency,high availability achieved with its robust architecture. Review collected by and hosted on G2.com.

Minimal featureset to support growing needs. Review collected by and hosted on G2.com.

Aeorospike and team delivered on performance requirements and exceeded expectations. Consistently getting 1-2ms latency on 1B requests per day. Review collected by and hosted on G2.com.

Custom hardware required to meet these demands. Some complexity on loads and space management. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

We really liked Aerospike, but as our use case was about Analytics 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 consist 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. Review collected by and hosted on G2.com.

We enjoy the reliability that Aerospike provides. Along with an ease of setup, it makes it a wonderful product. Review collected by and hosted on G2.com.

Not a ton of community support, most problems need Aerospike support to be fixed. Review collected by and hosted on G2.com.

Ease of use, mgmt is easy, and also quick lookups based on keys. Review collected by and hosted on G2.com.

No direct export or import from hadoop. Have to write a mapreduce job just to load data into aerospike. Review collected by and hosted on G2.com.

Aerospike stores index in RAM, so it's really extremely fast. It uses the full power of the SSD devices to provide maximum performance and low latency for both read and writes.

Aerospike is not just key-value storage. It provides you a rich set of data structures, which allow you to flexibly store and query data.

Applications do not need to know where to send the data. Aerospike clients are cluster aware, so they automatically send data directly to the node with the data. It allows you to easily build even large clusters. Review collected by and hosted on G2.com.

Not all flash devices can handle the high volume of transactions required by Aerospike Database. You need to use devices from the certified list: http://www.aerospike.com/docs/operations/plan/ssd/ssd_certification.html It's reasonable, but sometimes could be painful, because you need to benchmark nearly every device before using it in production.

Also, you need to carefully plan your storage. Aerospike stores index in RAM, so double-check that your data can fit into RAM. Review collected by and hosted on G2.com.

We had a special use case for our business where we needed a NoSQL clustered database that is highly available and must possess highly concurrent, low latency, transactional, small updates to billions of entries with ~10x more read than write volume. We ran a detailed review, analysis, and benchmark of Cassandra vs Aerospike, these famous ones in that aspect - Aerospike was clearly the winner here. What our management loved most about Aerospike was stable predictable performance with low latency and no hassle with maintenance. It's so simple and effective to manage keys in Aerospike that it actually turned out to be a very cost-effective and time-saving feature of Aerospike for our team. Review collected by and hosted on G2.com.

Cost can be a big issue for someone not so quite familiar with the working model of Aerospike. Not saying it's something wrong on Aerospike's end, but users need to be careful deploying their keys. The larger the keyspace of keys deployed with Aerospike, the more expensive your Aerospike cluster will be from a hardware point of view because all keys are stored in memory whether it's in memory or SSD form. This model is quite different than Cassandra, since all keys and values are stored on hard disk. Review collected by and hosted on G2.com.