Redis Cloud - Annual
RedisExternal reviews
External reviews are not included in the AWS star rating for the product.
Effortless Scalability with Active-Active Geo-Replication
Amazing Product for Main Cache Provider, No Complaints
Redis Database review
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.
Optimize AI projects with reliable data processing while addressing scaling challenges
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Which solution did I use previously and why did I switch?
How was the initial setup?
What about the implementation team?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
DO NOT opt for Private offering with REDIS
The redis private offering is not transparent. It is one way agreement wherein the customer cannot disengage if not satisfied by the product or service. Also, redis continues to keep invoicing even for unused services as long as the private offer is active (which BTW the customer cannot disable/deactivate/unsubscribe without redis intervention). And moreover redis team - specifically in India is not collaborative in this case as they will not cancel/disable the subscription and not even respond to the customer requests as such.
So recommended NOT TO OPT for any such traps where there is no exit in control of the customer.
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?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Efficient inter-thread communication, good with managing query caches and offers an easy setup
What is our primary use case?
In my current workplace, we use Redis for various purposes, including managing query caches, queues, and as a registry for different system components. These components register themselves when live, enabling efficient usage tracking.
Previously, at another company, we used Redis to cache machine learning models, facilitating model delivery across platforms without frequent disk retrieval.
How has it helped my organization?
In my current workplace, we use Redis for various purposes, including managing query caches, queues, and as a registry for different system components. These components register themselves when live, enabling efficient usage tracking.
Previously, at another company, we used Redis to cache machine learning models, facilitating model delivery across platforms without frequent disk retrieval.
What is most valuable?
Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle. We primarily use Redis as a caching system due to its multiple data types and PubSub features, offering efficient data handling. Redis's PubSub capabilities benefit our communication by facilitating thread intercommunication. It allows multiple threads to exchange messages efficiently.
What needs improvement?
Redis presents a single point of failure and lacks fault tolerance. It would be beneficial if high availability features were available in the noncommercial version, similar to those offered by the commercial managed solutions from Redis Labs.
For how long have I used the solution?
I have been working with Redis for over ten years.
What do I think about the stability of the solution?
If Redis is set up correctly, it requires no maintenance and can function smoothly for long periods without intervention. Memory calculations should be precise to avoid issues.
What do I think about the scalability of the solution?
With approximately 500 microservices and environments scaling up to 1,000 customers, Redis accommodates a range of scales. Proper memory allocation allows for seamless operation.
How are customer service and support?
We have not utilized customer support for Redis.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
In comparison to other caching solutions like Memcached and Aerospike, Redis is easier to deploy and manage. Aerospike, while highly efficient, is more complex to set up.
How was the initial setup?
The initial setup of Redis is very straightforward and user-friendly. Deploying Redis takes about thirty seconds, making it quick and efficient.
What about the implementation team?
Implementation can be done in-house using AWS ElasticCache or Docker to run Redis on Kubernetes, depending on cost and environmental factors.
Which other solutions did I evaluate?
We use Kafka for inter-process communication, but Redis is used for thread intercommunication due to its PubSub capabilities.
What other advice do I have?
I recommend Redis as it provides an easy-to-use caching solution with beneficial PubSub features.
It's excellent for startups or new projects with many components needing coordination. However, for more advanced messaging or larger data volumes, Redis might not be the best fit.
I rate Redis a nine out of ten.
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.