Likelihood to Recommend Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.
Read full review Riak is well suited to applications such as:
Transaction logging e.g. financial transactions and/or exchange rates.
Storing time series data, especially IoT.
Storing massive amounts of data e.g. corporation wide backups, data lakes etc.
A fully s3 compatible replacement for Amazon s3 ensuring data privacy.
Riak is not as well suited to:
Traditional RDBMS functions, especially those that join the outputs of one or more queries together to produce the desired result.
Read full review Pros Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency. Reliable. With a proper multi-node configuration, it can handle failover instantly. Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency. Fast. We process tens of thousands of RPS and it doesn't skip a beat. Read full review Highly available: If nodes go offline for any reason, the system still operates. Highly scalable: There is a minimum of 5 nodes, which can handle a lot by themselves. When scaling is required, it can be done easily, with minimal to no downtime on large scales. Very fast searching: Riak has SOLR indexing built-into the core product, which makes querying for data very fast. Read full review Cons We had some difficulty scaling Redis without it becoming prohibitively expensive. Redis has very simple search capabilities, which means its not suitable for all use cases. Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it. Read full review Deletes!!! We've seen on numerous occasions where Riak has "resurrected" deleted data. We've worked with Basho numerous times and tried multiple changes to the way we interact with Riak to prevent the problem but it still remains. The deletes seem to reappear weeks, even months, after the delete was issued. We've had to work around this issue by providing a "deleted" flag for all data objects stored in Riak. Thus, we do no delete but simply flip the flag. Excess baggage we would really like to not have to worry about. Search. Currently there's no way to tell what data you have in Riak without already knowing a particular bucket/key. There is a way to list the keys for a given bucket but due to performance implications, this is not a viable method to lookup data. Especially when you have a large amount of keys in the bucket. Read full review Likelihood to Renew We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.
Read full review Right now, I'm on a project where we need databases that can run on embedded systems. Riak isn't necessarily the best fit for that scenario. But when we need a clustered database, that's where we'd start considering Riak.
Read full review Usability It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.
Read full review Support Rating The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.
Gene Baker Vice President, Chief Architect, Development Manager and Software Engineer
Read full review Despite Basho going bankrupt and the project becoming fully open-source, community support is reasonably good, albeit a little slow at times. Paid enterprise-grade support is also available from former Basho engineers but the same company also contributes to the community support for free for basic questions or specific knowledge areas.
Read full review Implementation Rating Whitelisting of the AWS lambda functions.
Read full review Alternatives Considered We are big users of
MySQL and
PostgreSQL . We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Read full review Because of the RESTful HTTP interface, the consistency model, and because of the catalog-driven data model, Riak was an easy win over
Redis and Memcached.
Read full review Return on Investment Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides. Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues. Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment. Read full review Riak has been a key part of our company's build process for our client's search backend. It is valuable for is in that it provides a reliable way to view the current search index. Read full review ScreenShots