External reviews are not included in the AWS star rating for the product.
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.
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.
It performs much better than traditional databases. Our calculations happen in real-time, which was crucial for that quiz feature.
The price could be better.
I have been using it for more than two years.
It has been a reliable product for us.
It's been working very well for us. Since our scale isn't huge, it's able to handle our needs without issues.
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.
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.
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.
I have been using a specific infrastructure. We use it primarily for customer service.
It makes operations more efficient. The information processing is very fast, and very responsive. It's all about the technology.
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.
My experience with this product has been very good.
It's been very stable. I would rate the stability a ten out of ten.
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.
I would rate it an eight out of ten.
I would recommend to explore this product as it's gonna make the work easy.
We use Redis for caching and to improve the speed of the database.
The product offers fast access to my database.
I have been working with the product since 2022.
Since implementing the product, we have experienced stability in our applications.
The solution is scalable.
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.
Redis is an open-source product.
I rate the product an eight out of ten.
Sometimes, Redis is used as a cache and sometimes as the main database.
Redis is a simple, powerful, and fast solution.
Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application.
I have been using Redis for three years.
I rate Redis a seven or eight out of ten for stability.
In our team, around 20 to 25 engineers are using the solution.
I rate Redis a nine or ten out of ten for scalability.
The solution's technical support team was quite knowledgeable and fast.
Positive
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.
The solution’s initial setup is easy.
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.
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.
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.
I use the solution for saving user sessions and user data for different applications.
The online interface is very fast and easy to use.
There is a lack of documentation on the scalability of the solution.
The product should create awareness about its scalability.
I have been using the solution for five years.
The solution is very stable.
The product is very scalable.
The initial setup is easy.
The deployment could take one to two weeks.
People using the solution should be aware of all the features of the solution. Overall, I rate the solution a ten out of ten.