External reviews
61 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Optimize AI projects with reliable data processing while addressing scaling challenges
What is our primary use case?
We use Redis for several purposes, including ranking, counting, saving, sharing, caching, and setting time-to-live notifications. These functionalities are employed across various AI projects and in data processing tools, where Redis helps with the ongoing data pipeline process.
What is most valuable?
Redis has multiple valuable features such as being a free and reliable open-source tool. It functions similarly to a foundational building block in a larger system, enabling native integration and high functionality in core data processes. Despite its limitations, Redis provides valuable performance enhancement through system fine-tuning and multi-thread handling.
What needs improvement?
There are a few areas where Redis could improve. The pub-sub capabilities could be optimized to handle network sessions better, as there are challenges with maintaining sessions between clients and systems. Data persistence and recovery face issues with compatibility across major versions, making upgrades possible but downgrades not active. There's a need for better migration tools to support data movements in a hybrid environment. Concerns exist about licensing and community engagement due to changes in Redis and its forks.
For how long have I used the solution?
I have been working with Redis for maybe ten years.
What was my experience with deployment of the solution?
We encountered several challenges during the deployment process. Redis required a comprehensive setup process, with attention to hosting parameters, environment preparation, and network rules configuration. It is particularly complex in high-performance scalability contexts, taking us around one week to deploy initially.
What do I think about the stability of the solution?
Redis is fairly stable, although improvements are needed concerning user load and direct answering time, which sometimes results in downtime on the user side.
What do I think about the scalability of the solution?
Redis is somewhat limited in scalability, rating around four or five. Data migration and changes to application-side configurations are challenging due to the lack of automatic migration tools in a non-clustered legacy system.
Which solution did I use previously and why did I switch?
We have been using Redis since before I joined the company, so I am unaware of any previous solutions.
How was the initial setup?
The initial setup of Redis was difficult, with a rating of two or three out of ten. A deep understanding of Redis’s core and high technical knowledge was required, making the process lengthy and complex.
What about the implementation team?
Our implementation was handled internally by a small team. Typically, deploying Redis requires participation from around two or three people.
What's my experience with pricing, setup cost, and licensing?
Since we use an open-source version of Redis, we do not experience any setup costs or licensing expenses. The solution is integrated and utilized internally without financial investment.
Which other solutions did I evaluate?
We did not evaluate other solutions before selecting Redis, as it was already decided by the time I joined the company.
What other advice do I have?
I rate Redis seven out of ten overall. While it's a powerful open-source tool, it has areas needing improvement in terms of scalability and certain functionalities. Despite this, the tool provides reliability for our needs. I recommend considering these aspects before adopting Redis for large-scale operations, especially if high technical competencies are needed.
Which deployment model are you using for this solution?
Hybrid Cloud
Helps to store and load static content for multi-client products
What is our primary use case?
Our organization's main use case for Redis is to store and load static content for our multi-client products.
What is most valuable?
The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data.
What needs improvement?
The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly.
How are customer service and support?
I haven't contacted technical support yet.
What's my experience with pricing, setup cost, and licensing?
The tool is open-source. There are no additional costs.
What other advice do I have?
If you have a large amount of non-dynamic data that needs to be delivered to the client, you should use Redis. I don't think that it will support AI initiatives since it doesn't support continuous data. I rate the overall solution a seven out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Best in class in memory data store
What do you like best about the product?
Many problems are addressed by Redis. Few of them are Session cache, Redis can be used as a middle layer.
What do you dislike about the product?
Not easy to use.
There will be only one Master with multiple slaves for replication.
All write goes to Master, which creates more load on master node
If Master goes down, whole architecture is prone to SPOF (Single point of failure).
There will be only one Master with multiple slaves for replication.
All write goes to Master, which creates more load on master node
If Master goes down, whole architecture is prone to SPOF (Single point of failure).
What problems is the product solving and how is that benefiting you?
Its fast, if a lot of data has to be shown in a dashboard, the most important or the frequently accessed ones can be saved in a redis data store and the remaining can be saved in any SQl/NoSQL database
My go-to Redis-as-a-service provider
What do you like best about the product?
Redis Cloud integrates well with Heroku and AWS S3, and it makes getting up and running a breeze. Their ability to effortlessly upgrade/downgrade plans without any interruption is incredibly valuable.
What do you dislike about the product?
The web-UI for managing and interacting with your databases is fairly confusing, and often leaves you clicking around wondering which (similarly-named) section ends up holding the item you're looking for.
What problems is the product solving and how is that benefiting you?
Redis Cloud lets us quickly scale up and provision Redis instances as needed, on demand. Not having to manage these ourselves has been extremely valuable in freeing up resources for work elsewhere.
Recommendations to others considering the product:
We haven't spent a ton of time looking at other Redis-as-a-service offerings, but we've been pretty happy with our experiences with Redis Cloud. Their support has been fairly decent, as has the product – if it seems like it meets your needs and expectations, I'd say go for it.
showing 1 - 4