Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Summit 2019
What do you like best about the product?
Sessions where awesome. however the last part was finishing fast due to time constraint
What do you dislike about the product?
couldnt find anything wrong with the summit. all good.. keepup the good work . Will come again next year too.
What problems is the product solving and how is that benefiting you?
just learning we are already using AS
- Leave a Comment |
- Mark review as helpful
Aerospike
What do you like best about the product?
Fast nosql database, scale easily. Support is excellent.
What do you dislike about the product?
I find it hard to manage data storage, specifically had issues finding data size of specific sets. Wished there were better, easier tools.
What problems is the product solving and how is that benefiting you?
Caching speed.
Recommendations to others considering the product:
It's fast.
Blazing Fast, but Read the limitations before using
What do you like best about the product?
Aerospike has everything you would expect from a Key-Value store. Blazing Fast Write and Retrievals, Asynchronous Updates, UDFs, MultiFetches And a Feature Loaded Java API.
It performs as fast as In-Memory, when used with SSDs.
This can be the go-to Database for all sorts of caching Requirements in your company.
What surprised me was that, their update-modes and atomic Commands work like a charm.
It performs as fast as In-Memory, when used with SSDs.
This can be the go-to Database for all sorts of caching Requirements in your company.
What surprised me was that, their update-modes and atomic Commands work like a charm.
What do you dislike about the product?
The non configurable Limitations like 14 char limit on Bin Name, totally defeats the purpose of using it for storing multi-bins, or json like data.
We had to store the mappings separately, of the actual bin names to a 14 char truncated BinName, and use it at the time of Writing and also Reading.
We had to store the mappings separately, of the actual bin names to a 14 char truncated BinName, and use it at the time of Writing and also Reading.
What problems is the product solving and how is that benefiting you?
I used it as a product cache, for e-commerce data. Where various attributes of the products were to be stored against their SKUs.
We chose it over Redis, for it's ability to store a record as Bins. The feature loaded Java API and blazing fast write-and-retrieval on the Primary Key made it fit for the requirement.
We chose it over Redis, for it's ability to store a record as Bins. The feature loaded Java API and blazing fast write-and-retrieval on the Primary Key made it fit for the requirement.
Easy to setup and best key value store
What do you like best about the product?
Easy to setup . easy lookups based on keys . Its much faster
What do you dislike about the product?
I dont have anything that i disliked in it.
What problems is the product solving and how is that benefiting you?
Storing and query large data sets
Recommendations to others considering the product:
Definitely Yes!
A SOLID, High-Velocity Key/Value NOSQL Database
What do you like best about the product?
Metadata was using a traditional NOSQL database based on open-source technology, but we experienced challenges with scale and speed as our database grew.
We selected Aerospike to replace MongoDB due to its the ease of use, simple configuration and high velocity reading and writing.
Along with the easy client development and support for async requests, we managed to boost our profiling algorithms and run twice as fast, enabling us to serve more customers in a shorter amount of time with even leaner hardware resources.
Switching to Aerospike broadened our capabilities and has helped support our company growth. We recommend Aerospike to any software company looking for a solid key/value database that is scalable, super fast and commercially ready.
We selected Aerospike to replace MongoDB due to its the ease of use, simple configuration and high velocity reading and writing.
Along with the easy client development and support for async requests, we managed to boost our profiling algorithms and run twice as fast, enabling us to serve more customers in a shorter amount of time with even leaner hardware resources.
Switching to Aerospike broadened our capabilities and has helped support our company growth. We recommend Aerospike to any software company looking for a solid key/value database that is scalable, super fast and commercially ready.
What do you dislike about the product?
We had no problems / issues installing or integrating Aerospike into our solution and architecture. Their documentation made it easy and we're experiencing no issues scaling it.
What problems is the product solving and how is that benefiting you?
Our major challenge was to support our exponentially growing database without sacrificing on our platform speed nor purchasing significant more infrastructure. The results were Aerospike were amazing as we were able to more than double our performance while keeping a lean cloud infra.
Recommendations to others considering the product:
Read the documentation, talk to other users- make sure to set the best foot forward with the implementation and you're up for a sweet ride.
Happy Customer
What do you like best about the product?
We enjoy the reliability that Aerospike provides. Along with an ease of setup, it makes it a wonderful product.
What do you dislike about the product?
Not a ton of community support, most problems need Aerospike support to be fixed.
What problems is the product solving and how is that benefiting you?
Storing and query large data sets
Aerospike - A high throughput, low latency distributed nosql datastore
What do you like best about the product?
Simplicity of the architecture. Ease of Operations. high concurrency,low latency,high availability achieved with its robust architecture.
What do you dislike about the product?
Minimal featureset to support growing needs.
What problems is the product solving and how is that benefiting you?
high concurrency concerns with webservice calls.
Recommendations to others considering the product:
If you are looking for high throughput, low latency ,high concurrency ,nosql distributed database cluster, aerospike fits the criteria and deserves an active test for your usecase.
Aerospike
What do you like best about the product?
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.
What do you dislike about the product?
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
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
What problems is the product solving and how is that benefiting you?
A database that is faster than HBase, and replicating data to an AWS cluster to allow our web servers there to access the same information.
Recommendations to others considering the product:
Well worth reading through their documentation. It is thorough (much better than some other products) and contains a lot of little nuggets that will save you time. It pretty much walks you through considering how to scale out your infrastructure, how to set it up once you know what your resource needs are, and how to perform basic maintenance. The troubleshooting section could use some help, but the community forums are also solid. Make sure you take their advice regarding SSDs.
PIQ's review
What do you like best about the product?
Ease of use, mgmt is easy, and also quick lookups based on keys.
What do you dislike about the product?
No direct export or import from hadoop. Have to write a mapreduce job just to load data into aerospike.
What problems is the product solving and how is that benefiting you?
Fast key value lookups needed, where others didn't work.
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 31 - 40