I use Redis as a tool in building projects, specifically for in-memory caching. My backend API uses Redis to cache information retrieved from the database.
External reviews
61 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Accelerates data retrieval with an in-memory search tool to speed operations
What is our primary use case?
What is most valuable?
Redis acts as an in-memory search tool that improves the speed of operations. By making operations faster, Redis allows for quicker data retrieval and enhances the performance of applications.
What needs improvement?
Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation.
Additionally, better documentation is needed to set up a secure Redis server with user authentication, as there are gaps and issues in this area.
For how long have I used the solution?
I have been using Redis for two to three projects recently, with a total experience of about five to six years.
What do I think about the stability of the solution?
Redis is quite mature and stable, and I haven't encountered any stability issues.
What do I think about the scalability of the solution?
Redis does not require scaling. It can be a central in-memory store for all scalable units of an application, and it is not necessary to have a duplicate copy of Redis.
How was the initial setup?
The setup is quite easy; I would rate it as eight out of ten. However, there might be some difficulties related to secure servers.
What's my experience with pricing, setup cost, and licensing?
Redis is a free tool available for on-premises installations. There's no cost associated with it as I haven't used any cloud services.
What other advice do I have?
Redis is a nice choice for building applications that require high turnaround times for user requests. It reduces turnaround time by building a cache solution based on Redis.
I rate it as eight out of ten.
Fast performance with scalable and seamless deployment
What is our primary use case?
I use Redis as a cache to store user sessions with login details and also some current status of the devices.
What is most valuable?
The performance of Redis is very fast. Its deployment is pretty easy when using it on ElasticCache, and I did not need to worry about scalability on AWS. It's pretty scalable and stable.
What needs improvement?
For the PubSub feature, we had to create our own tools to monitor the events.
For how long have I used the solution?
I have been using Redis for about six years.
What do I think about the stability of the solution?
The ElasticCache is pretty stable.
What do I think about the scalability of the solution?
I did not need to worry about it on AWS, so it's pretty scalable.
How are customer service and support?
I have never contacted the Redis support team.
How would you rate customer service and support?
Positive
What other advice do I have?
I would probably advise learning how to use command-line tools.
I'd rate the solution eight out of ten.
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 reliable solution that provides consistent results for university project success
What is our primary use case?
I used Redis for a one-time implementation while working on a college project. I implemented it locally on a machine and used it for a vector search.
How has it helped my organization?
Since it was a university project, it helped in providing a stable and efficient solution for my project needs. This enabled me to complete the project successfully and pass an exam.
What is most valuable?
Redis is stable, provides consistent results, and is fast. It is particularly efficient for cloud-based storage and operations.
What needs improvement?
Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud. It would be helpful if Redis could provide a one-stop solution for all data varieties, which would improve the integrity between different databases.
For how long have I used the solution?
I used Redis for about a day for the implementation.
What do I think about the stability of the solution?
Redis is definitely a stable product. It provided accurate and consistent results without any issues.
What do I think about the scalability of the solution?
Redis is a highly scalable product, especially since it effectively handles cloud-based storage, which is the most scalable option.
How are customer service and support?
I did not communicate with the technical support team, so I cannot provide a rating for customer service.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I also used Firest for my project and found it to be more suitable for my specific use case.
How was the initial setup?
The initial setup was very easy. The only requirement was to change the syntax from Redis to Firest and vice versa.
What about the implementation team?
I completed the implementation all by myself without needing any additional help.
What's my experience with pricing, setup cost, and licensing?
I used the free, open-source version of Redis, so I did not incur any costs. For personal use, a lower price is always better.
Which other solutions did I evaluate?
I evaluated and used Firest and several other databases for my project, including Crontabee and Cosmodb.
What other advice do I have?
Redis is beneficial for specific usage and domains. If Redis can handle various data types efficiently, it would become a comprehensive solution for any use case, potentially topping other databases. Its consistent results and free, open-source nature make it a solid choice.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
On-premises
Enables efficient caching and helps users fetch and save data quickly
What is our primary use case?
We use the solution as a caching layer.
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.
My Experience Using Redis Enterprise
What do you like best about the product?
Redis is one of the go to unstructured databases used as a caching tool to optimise your application's performance.
It stores your data in RAM for Faster read and write operations.
Redis Enterprise has multiple features for faster data Accessibility, Security, Performance and Loss of Data Security (Data Durability).
Features like active-active and active-passive replication ensure that data is always avalilabe in case of faliure.
Rules are easily configuralble to ensure unwanted data deletion, to take timely data dump in case of machine faliure.
Usig Redis to cache static data for your application can take off load from your database and make your application feel much faster
It stores your data in RAM for Faster read and write operations.
Redis Enterprise has multiple features for faster data Accessibility, Security, Performance and Loss of Data Security (Data Durability).
Features like active-active and active-passive replication ensure that data is always avalilabe in case of faliure.
Rules are easily configuralble to ensure unwanted data deletion, to take timely data dump in case of machine faliure.
Usig Redis to cache static data for your application can take off load from your database and make your application feel much faster
What do you dislike about the product?
Redis prioritise performance over durability, it requireses a lot of ram and its data snapshot mechanism is not that much duralble like other databases.
It also cannot build complex data relationships as it uses key value pair to store data.
It also cannot build complex data relationships as it uses key value pair to store data.
What problems is the product solving and how is that benefiting you?
Redis Helping to take load off of the main database, Hence incresing the performance of my application drastically.
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.
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?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
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.
Redis Review
What do you like best about the product?
It is a good tool for database management platforms, handle multiple users session, provide object-based information very fast. It is straightforward to install and is a very cost-effective solution. It gives the ability to manage and handle caching requirements and is thus very effective for performance. It can provide outstanding performance and efficiency with large amount of data also. Updates are pushed promptly and have rich community support. Helps business in growth
What do you dislike about the product?
Redis cluster needs to know to clients who manage it. Proper knowledge of topology and overhead configurations is required. Sometimes issue handling failovers inside the cluster due to master/slave node configuration issues. Redis doesn't provide local storage in object forms. Data serialization needs to be addressed.
What problems is the product solving and how is that benefiting you?
We use Redis as our data structure repository. It keeps key-value data store. It supports many datatypes, and caching helps the persistence of data. The speed of this system is phenomenal.
Redis Enterprise on multi cloud platform
What do you like best about the product?
the highest levels of availability in geographically distributed environments, effortless scaling to any dataset sizes, and significant cost reduction to enterprise customers
What do you dislike about the product?
It is a bit difficult task to learn how to use Redis from the documentation
What problems is the product solving and how is that benefiting you?
Redis supports data structure like Hash, String, Lists, and sets
showing 1 - 10