TrustRadius Insights for Aerospike are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Fast and Efficient: Users have consistently praised Aerospike for its fast and efficient performance. Many reviewers have stated that Aerospike provides sub-millisecond response times and high availability, making it a reliable and speedy database solution.
Easy to Use: Numerous users appreciate the easy-to-use nature of Aerospike. They find it highly efficient and user-friendly, allowing for easy maintenance and management. The straightforward user interface, along with features like managing sets and making queries using AQL, contributes to its ease of use.
Highly Stable: Reviewers have highlighted the stability of Aerospike as one of its key strengths. Many users describe it as a reliable system with minimal operational issues and high throughput at low latency. The fault-tolerant and consistent nature of Aerospike, along with great customer service, make it a stable choice for their database needs.
Aerospike Reviews
3 Reviews
Engineering
Search is temporarily unavailable. Filters are still applied.
My organization uses Aerospike to power applications that need access to data in real-time. It powers many different kinds of applications as it's a key-value database, graph database, JSON Document database, and a Vector database all-in-one. It's very resilient and once the cluster is up and running, it doesn't have any full cluster failures that impact our applications.
Best part is that we've been able to scale to hold 100s of TBs and haven't seen any performance degrade in terms of throughput and latency.
Pros
low latency database while deployed on SSDs (1ms-4ms)
high throughput database (supports our 600k+ ops/second application)
ability to scale-up and scale-out, enabling us to store 20TB cost efficiently
Cons
The developer experience could be a bit better
Community driven engagement is pretty low
No GUI for developer play around
Likelihood to Recommend
Its best suited for applications that need low latency, high throughput, while storing Terabytes of data on a single cluster
Aerospike is used to perform low-latency looks-up on our edge servers. Data is replicated out from a central cloud based cluster out to bare metal to mitigate costs. The low latency reads and ability to handle high volume writes with minimal errors is enormous in our industry.
Pros
Low latency
Stable
Highly configurable
increasing features
Cons
AQL is pretty limited and not as useful as the java client
Documentation can be lacking for some products
replication configuration is complicated
Likelihood to Recommend
Aerospike preforms great as an ultra low latency key value lookup, the java client is very robust and leads to easy development. I would say the additional/newer products specifically the kafka connector are rough around the edges for development but do blend nicely into the big data landscape.
Fastest KV lookup we ever did, by using Aerospike. Compared it to other KV lookups such as Redis, MemcacheD and Genie. The Aerospike database has become core to the company product itself. It essentially reduced lookups by 30% compared to redis and memcacheD. The core product of the company is adserving and was used as well for fraudulent clicks, and such.
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.
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..
Likelihood to Recommend
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.
