Redis Cloud - Annual
RedisExternal reviews
94 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-Memory Cache
What do you like best about the product?
A lot of useful data types to choose from such as hashes lists and self destroyed keys with timers
Fast read and write
Clustering and Distributing between servers
Fast read and write
Clustering and Distributing between servers
What do you dislike about the product?
Lack of documentation.
Difficulty running on Windows (sometimes).
Difficulty running on Windows (sometimes).
What problems is the product solving and how is that benefiting you?
We have an internall betting site that is used for training and risk management assestment.At advanced levels we required realtime and low latency results for our server sometimes. we got to a point where we can rely on our results accross the userbase and asses the risk and apply the bet.
Recommendations to others considering the product:
Fast, Complete,Reliable and most fun to experiment with.
Redis for in Memory Storing.
What do you like best about the product?
I like the speed of Redis. Where I usually using Redis for storing the Authentication tokens in the memory. And it returns the response in no time. This can be accessed as a service using a HOST and a PORT, it allowed us to use Redis in a versatile infrastructure. Mostly we can use it as a sharable(Centralised) data store can be accessed from varies ends, it helps us to setup load balanced infrastructure with multiple application mirror servers.
What do you dislike about the product?
Poor querying ability is the only minus I don't like.
What problems is the product solving and how is that benefiting you?
I saved authentication token in a single sharable Redis Server, which can be accessible from multiple application servers.
Very quick server DataStore
What do you like best about the product?
Redis comes in a very light and fast environment which allowed me to run my test on an old Raspberry Pi without lags due to computation times.
What do you dislike about the product?
There is a big lack of documentation both on official website that on online tutorial.
Moreover the event management is quite poor (but under active development).
This, in addition to the weird syntax, caused a little of problems in getting started with it.
Moreover the event management is quite poor (but under active development).
This, in addition to the weird syntax, caused a little of problems in getting started with it.
What problems is the product solving and how is that benefiting you?
I was working on a disaster-management mobile application and Redis was the datastore selected on server to manage the data because of it's impressive speed (which was a requirement in the development context).
Recommendations to others considering the product:
If you are looking for a very fast datastore, Redis may be what you are looking for. Please be aware that it is so fast because it saves all (of most) of the storage directly on RAM, therefore it requires a server with a lot of primary memory in order to exploit it's full potential. This may lead to an increment of costs which should be considered.
Redis has a log file on disk with the history of all action performed which is used in case of recovery. By default this log is updated asyncronously at certain time intervals, this means that if a problem occours between two interval, it may lead to a data loss. It is configurable to update on log on each action, but this has to be bechmarked as may reduce performances.
Redis has a log file on disk with the history of all action performed which is used in case of recovery. By default this log is updated asyncronously at certain time intervals, this means that if a problem occours between two interval, it may lead to a data loss. It is configurable to update on log on each action, but this has to be bechmarked as may reduce performances.
Redis - replacing AppFabric
What do you like best about the product?
Fundamentally simple enough concepts.
Lots of resources, can learn fairly the whats and hows.
Lots of resources, can learn fairly the whats and hows.
What do you dislike about the product?
no automated persistence of what gets changed in the cache
What problems is the product solving and how is that benefiting you?
Acceleration of reads for frequently-used complex data
Recommendations to others considering the product:
Usual PoC approach. Don't assume that, since it worked fine for others, it'll work for you too out of the box, even if use cases are very similar. One should learn it hands-on - no different from other critical infrastructure components.
showing 1 - 6