Redis is used for a part of a booking engine for travel, specifically for the front part to get some sessions and information about the sessions. If a customer or user is using the sites in different parts, we use Redis to get this information in cache.
External reviews
61 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Performance shines with seamless session caching and minimal configuration
What is our primary use case?
What is most valuable?
The best features of Redis, from my personal perspective, are the performance, which is very quick, and it's very simple to implement.
Since I started using Redis, I feel that the product is saving me some performance tuning time. It's very easy, I have few parameters to tune, and it seems to have performance without a lot of working on the performance, compared to Cassandra, where you have to configure the memory and many other settings.
The integration capability of Redis is excellent.
Redis is very affordable because it's free.
What needs improvement?
The disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters. The sync between the nodes is easier to implement with Couchbase, for example, and this is the only problem, the only disadvantage for me.
For how long have I used the solution?
I started using Redis this year.
What do I think about the stability of the solution?
The stability of Redis rates nine out of ten, with one being not stable and ten being very stable.
What do I think about the scalability of the solution?
The scalability of Redis rates eight out of ten, with one being not scalable and ten being very scalable.
How are customer service and support?
Technical support rates at three out of ten.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We started using Redis this year when we switched from Couchbase at the beginning of the year.
I have decommissioned Couchbase, which was not my database but my customer's database. They decommissioned it this year and chose Redis for the cache data parts, so I'm not using Couchbase anymore.
What about the implementation team?
We use community support and we don't have a provider for the support, but to be honest, we don't need support. From the time we implemented, I hope it will continue this way.
What was our ROI?
I see about 40% savings since using Redis.
Which other solutions did I evaluate?
In my projects, we use documents basically, so all the NoSQL databases can be mapped with an API to have a kind of independence from Redis and any tool. If tomorrow we want to move from Redis to something better, we are independent from that.
What other advice do I have?
If Redis has questions or comments related to my review, it's possible for them to reach me via email to clarify something.
I am interested in being a reference for Redis.
On a scale of 1-10, I rate Redis a 10.
Which deployment model are you using for this solution?
On-premises
Redis key deploying
What do you like best about the product?
The each entry of Redis cashes to maintain ttl for long time as per our request
What do you dislike about the product?
The maintenance window which was managed by Redis team
What problems is the product solving and how is that benefiting you?
Redis Cloud is solving several critical problems that developers and businesses face when managing high-performance, real-time applications.
Simplified caching with a user-friendly UI and easy setup
What is our primary use case?
I primarily use Redis as a cache to store the most requested files, folders, and URLs. This makes retrieval fast and has minimal latency.
What is most valuable?
Redis is a simple service that does what it promises. We use it through AWS, and it's not managed by us. There is no operational overhead thanks to Amazon. It is highly available, reliable, and functions exactly as expected, eliminating the need to reinvent the wheel with cache.
What needs improvement?
There is room for AWS to provide more options for server types or a way to configure more or less memory for them.
For how long have I used the solution?
I have been using Redis for about four years.
What do I think about the stability of the solution?
Redis is 100% stable for our needs. We haven't experienced any complaints or issues related to stability.
What do I think about the scalability of the solution?
AWS allows you to change the cluster size for Redis easily. However, I am unsure if horizontal scaling is possible.
How was the initial setup?
Using AWS for Redis, the setup involves going through a user-friendly UI, making the process simple and straightforward. After setup, you get an endpoint, and it's ready to use.
What's my experience with pricing, setup cost, and licensing?
We use Redis through AWS, so we pay related costs monthly as specified by Amazon.
What other advice do I have?
I rate Redis a ten out of ten. There might be some improvement needed by allowing more configuration options regarding resources available for the servers.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Fast caching and vector search
Easy to use, moved from Redis OSS to Redis Cloud to cache my data as JSON and use vector search for some new search functionality our team is building with langchain and RedisVL.
Easy signup from AWS marketplace
I'm just starting to use Redis. Signup was easy and the free trial in the Redis app was a good way to save $ while trying it out.
Fast single-threaded solution for large datasets and effective concurrency management
What is our primary use case?
In the past, I used Redis as a cache, and currently, I'm using it as a messaging system.
How has it helped my organization?
Redis is pretty fast compared to others, making it a reliable choice. It's much more reliable and helps with our message broker functionalities.
What is most valuable?
Redis is a single thread, which is one of the key features I like. Redis is also pretty fast, and many of our use cases are satisfied with its single-threaded nature. This feature helps us manage concurrency effectively.
What needs improvement?
I don't think there's any room for improvement as it's been good for large-scale use and large datasets.
For how long have I used the solution?
I have been using Redis for almost three years now.
What do I think about the stability of the solution?
I haven't faced any issues from a performance, outage, or availability point of view. It's good.
What do I think about the scalability of the solution?
It's very easy to scale up and scale down. I'd say it's highly scalable.
How are customer service and support?
I didn't get a chance to interact with their support team.
How would you rate customer service and support?
Positive
What other advice do I have?
Use Redis wisely because it is a single-threaded tool. There was an issue we faced in the past where a query was not optimized, which impacted performance significantly.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Has interesting algorithms like HyperLogLog and provides useful features
What is our primary use case?
I've used Redis mainly to improve application performance through caching. I've also used it as a small project broker and an external lock mechanism. I used it in previous companies.
What is most valuable?
What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting.
For how long have I used the solution?
I have been using the solution for eight years.
What do I think about the stability of the solution?
I haven't faced any stability issues.
What do I think about the scalability of the solution?
I rate the tool's scalability an eight out of ten.
What's my experience with pricing, setup cost, and licensing?
Redis is an open-source solution.
What other advice do I have?
I rate the overall solution a ten out of ten.
Used for data deduplication or identifying duplicate records
What is our primary use case?
I use Redis for data deduplication or identifying duplicate records I receive. I have a very basic usage with Redis, where I insert a key value record.
What is most valuable?
The solution is fast, provides good performance, and is not too expensive. Although installing it locally would probably be cheaper, I don't want the hassle. For the functionality I need, Redis gives me what I want at the moment.
What needs improvement?
The solution's pricing for a local installation is very expensive.
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 haven’t faced any issues with the solution’s stability.
What do I think about the scalability of the solution?
Azure allows Redis to scale. If I want, I can increase the resources allocated for this service.
How was the initial setup?
I'm using the solution as an Azure cloud service with no installation involved.
What was our ROI?
The solution does what I need, and I have no issues with it. Since I didn't install Redis and don't need to maintain it, the service saves me a lot of time.
What other advice do I have?
Overall, I rate the solution ten out of ten.
A simple open source solution with good caching capabilities and managing key-value pairs for handling cache requests effectively
What is our primary use case?
I'm the only user utilizing Redis in my company, as my platform is relatively new and has around fifty users. However, in my previous role at Profit Clicks, we had approximately ten thousand users. We utilized a combination of databases, including Redis, MongoDB, and MariaDB. We needed to handle push notifications for our users, sending them three times a day, and managing a large volume of notifications efficiently was crucial. Redis played a role in managing this workload.
What is most valuable?
I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios.
What needs improvement?
There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient.
For how long have I used the solution?
I have been working with Redis for the last year approximately.
What do I think about the stability of the solution?
Redis is stable and works well without any issues on my end. I occasionally encounter problems with MongoDB because MongoDB has a very different stack.
What do I think about the scalability of the solution?
It is a scalable solution.
How was the initial setup?
Redis requires occasional maintenance, but it is generally a low-maintenance solution and is straightforward to manage. I haven't encountered any difficulties or downtime after updates, as Redis is robust and concise.
What other advice do I have?
I haven't explored AI-driven initiatives yet, but they are on my road map. I would recommend Redis for all kinds of caching and message brokering needs. It's a reliable and straightforward solution.
Overall, I would rate Redis ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
A scalable solution with a very fast and easy-to-use online interface
What is our primary use case?
I use the solution for saving user sessions and user data for different applications.
What is most valuable?
The online interface is very fast and easy to use.
What needs improvement?
There is a lack of documentation on the scalability of the solution.
The product should create awareness about its scalability.
For how long have I used the solution?
I have been using the solution for five years.
What do I think about the stability of the solution?
The solution is very stable.
What do I think about the scalability of the solution?
The product is very scalable.
How was the initial setup?
The initial setup is easy.
What about the implementation team?
The deployment could take one to two weeks.
What other advice do I have?
People using the solution should be aware of all the features of the solution. Overall, I rate the solution a ten out of ten.
showing 1 - 10