We use the solution as a caching layer.
Redis Cloud - Annual
RedisExternal reviews
External reviews are not included in the AWS star rating for the product.
Enables efficient caching and helps users fetch and save data quickly
What is our primary use case?
What is most valuable?
The ability to fetch and save data quickly is valuable. We can fetch data within milliseconds. The tool provides data structure capabilities. It also provides geolocation search and JSON search capabilities. The performance is very good. Redis can save each internal transaction to the file system. It helps us handle persistence in our storage.
What needs improvement?
The product's main purpose is caching, even though the vendor says we can also use it as a persistent database. If we use a lot of data, it will eventually cost us a lot. The tool is single-threaded. It doesn't support many data models. We only have key-value, hash, and JSON.
For how long have I used the solution?
I have been using the solution for more than ten years.
What do I think about the stability of the solution?
The tool is stable.
What do I think about the scalability of the solution?
The tool is easy to scale. We can add additional storage, and it will scale easily. We have millions of end users. We are an enterprise-level organization.
How are customer service and support?
The product provides excellent support.
How would you rate customer service and support?
Positive
How was the initial setup?
The deployment is easy. The deployment takes a couple of hours. One engineer can deploy the tool. We can fully manage the tool as SaaS with low maintenance. If we want to deploy it in our own environment, we must be more aware of changes and monitoring. Since I'm using the caching layer, we must choose the correct mode to save and fetch the data optimally. It is complicated to understand which feature or model we must use.
What was our ROI?
Eventually, we need to manage caching. If we manage on our own, it will take a lot of developer resources, infrastructure, and environmental resources. So, it is better to use Redis. The ROI is better.
What's my experience with pricing, setup cost, and licensing?
We pay a yearly fee, but we pay according to the usage.
Which other solutions did I evaluate?
I also work with PostgreSQL, MySQL, Elasticsearch, Cassandra, and Splunk. Redis provides efficient caching and performance. The other solutions have persistent storage functionality. If I want persistence, I would use the other tools. If I need high performance, I would use Redis.
What other advice do I have?
We must understand our system needs and pick the correct data structure in Redis to support it most efficiently. Overall, I rate the tool an eight out of ten.
Performs much better than traditional databases, integrates well and lot of learning resources available
What is our primary use case?
We use it primarily for real-time applications. In our web application, we added a feature where hundreds of people could play a quiz in real time.
Instead of using traditional databases like SQL, we implemented Redis to make everything happen in real time – all those quick calculations, data hashing for easy retrieval, and so on.
It was a live quiz feature, so Redis helped a lot. I also use Redis for caching and similar general use cases.
How has it helped my organization?
It improved the performance. For example, data structures like hashmaps in Redis make it a very fast database – much faster than traditional SQL databases. It can perform at significantly higher speeds. Latencies are very low. Our primary focus wasn't on saving money but on improving performance for that specific feature.
So, performance has been the key improvement. Every calculation happened in real time. It improved the performance 10X.
In our company, we have limited resources, so we can't manage the database ourselves. We use services from Azure for that. So, Redis integrates well with those services.
We use Azure Cache for Redis.
What is most valuable?
It performs much better than traditional databases. Our calculations happen in real-time, which was crucial for that quiz feature.
What needs improvement?
The price could be better.
For how long have I used the solution?
I have been using it for more than two years.
What do I think about the stability of the solution?
It has been a reliable product for us.
What do I think about the scalability of the solution?
It's been working very well for us. Since our scale isn't huge, it's able to handle our needs without issues.
Which solution did I use previously and why did I switch?
I've also worked with PostgreSQL, Cassandra, MySQL, and Elasticsearch.
It's tough to find a direct competitor because Redis, Cassandra, PostgreSQL, and Elasticsearch all serve different purposes. Cassandra excels when you structure tables according to your requirements upfront. It offers fast reads. However, the Cassandra Query Language (CQL) isn't as flexible as SQL – there are no joins, for example. It is a very restricted query language. So, we need to carefully design your database tables with future data needs in mind.
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you use Redis efficiently.
What's my experience with pricing, setup cost, and licensing?
It's actually quite expensive compared to SQL since Redis uses a system's main RAM, which is costly. And memory can be limited.
We opt for a dedicated server.
What other advice do I have?
Overall, I would rate the solution an eight out of ten. It's been very stable so far and performs well within our system.
I would recommend it, but I would also highlight the cost factor as something to consider.
Redis: The most useful Database as cache.
Best cache for Application
Fast data processing able to read write vesy fast.
Offers good stability and information processing is very fast
What is our primary use case?
I have been using a specific infrastructure. We use it primarily for customer service.
What is most valuable?
It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology.
What needs improvement?
The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier. But no one provided a GUI, or maybe we didn't request it. I'm not sure. We just make use of it.
For how long have I used the solution?
My experience with this product has been very good.
What do I think about the stability of the solution?
It's been very stable. I would rate the stability a ten out of ten.
What was our ROI?
We saw an ROI. It made the processing of our transactions faster. So there are some details we get, like customer contract details, customer details, customer ID, there are so many details for that. So we get it from Redis, which makes it faster.
What other advice do I have?
I would rate it an eight out of ten.
I would recommend to explore this product as it's gonna make the work easy.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Improves database speed and helps with caching
What is our primary use case?
We use Redis for caching and to improve the speed of the database.
How has it helped my organization?
The product offers fast access to my database.
For how long have I used the solution?
I have been working with the product since 2022.
What do I think about the stability of the solution?
Since implementing the product, we have experienced stability in our applications.
What do I think about the scalability of the solution?
The solution is scalable.
How was the initial setup?
The initial setup took some time as our technical team needed to familiarize themselves with Redis. Once they gained expertise, the deployment process became straightforward and was completed within a month and a half. A seven-member team helped with the deployment.
What's my experience with pricing, setup cost, and licensing?
Redis is an open-source product.
What other advice do I have?
I rate the product an eight out of ten.
A simple, powerful, and fast solution that can be used as a main database
What is our primary use case?
Sometimes, Redis is used as a cache and sometimes as the main database.
What is most valuable?
Redis is a simple, powerful, and fast solution.
What needs improvement?
Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application.
For how long have I used the solution?
I have been using Redis for three years.
What do I think about the stability of the solution?
I rate Redis a seven or eight out of ten for stability.
What do I think about the scalability of the solution?
In our team, around 20 to 25 engineers are using the solution.
I rate Redis a nine or ten out of ten for scalability.
How are customer service and support?
The solution's technical support team was quite knowledgeable and fast.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used other solutions like DynamoDB, Elasticsearch, and Postgres for different use cases. We switched to Redis because maintaining the cluster for Elasticsearch was very complex and a lot of work. Also, the other solutions were very, very expensive.
How was the initial setup?
The solution’s initial setup is easy.
What about the implementation team?
Since we're using the AWS self-managed version, Redis can be deployed very fast if you go through the console. If you do an infrastructure, its setup will take longer. But if you just want to play with it and set it up quickly, it can be done in 10 to 15 minutes or less.
What's my experience with pricing, setup cost, and licensing?
The solution's pricing is good compared to other databases doing the same thing. It might be cheaper to use Redis in some cases and not in others. Redis is not an overpriced solution.
What other advice do I have?
Redis is deployed on-cloud in our organization.
When it started, Redis had a very simple structure, but now it has a lot of powerful data structures. Users should investigate because they can use other things for their data structure. Redis has more new use cases. Users must consider that Redis is single-threaded, which might take a toll on them when they write to Redis. This might be an issue if you need very high throughput with writes.
Overall, I rate Redis a nine out of ten.
Top caching tech
The open source, in-memory data store
It is open source and very well documented.
It consumes a lot of RAM.