I have been using a specific infrastructure. We use it primarily for customer service.
Redis Cloud - Annual
RedisExternal reviews
94 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Offers good stability and information processing is very fast
What is our primary use case?
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.
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.
A simple, powerful, and fast solution that can be used as a main database
What is our primary use case?
Sometimes, Redis is used as a cache and sometimes as the main database.
What is most valuable?
Redis is a simple, powerful, and fast solution.
What needs improvement?
Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application.
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 rate Redis a seven or eight out of ten for stability.
What do I think about the scalability of the solution?
In our team, around 20 to 25 engineers are using the solution.
I rate Redis a nine or ten out of ten for scalability.
How are customer service and support?
The solution's technical support team was quite knowledgeable and fast.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used other solutions like DynamoDB, Elasticsearch, and Postgres for different use cases. We switched to Redis because maintaining the cluster for Elasticsearch was very complex and a lot of work. Also, the other solutions were very, very expensive.
How was the initial setup?
The solution’s initial setup is easy.
What about the implementation team?
Since we're using the AWS self-managed version, Redis can be deployed very fast if you go through the console. If you do an infrastructure, its setup will take longer. But if you just want to play with it and set it up quickly, it can be done in 10 to 15 minutes or less.
What's my experience with pricing, setup cost, and licensing?
The solution's pricing is good compared to other databases doing the same thing. It might be cheaper to use Redis in some cases and not in others. Redis is not an overpriced solution.
What other advice do I have?
Redis is deployed on-cloud in our organization.
When it started, Redis had a very simple structure, but now it has a lot of powerful data structures. Users should investigate because they can use other things for their data structure. Redis has more new use cases. Users must consider that Redis is single-threaded, which might take a toll on them when they write to Redis. This might be an issue if you need very high throughput with writes.
Overall, I rate Redis a nine out of ten.
The open source, in-memory data store
What do you like best about the product?
Is a very fast key/value data store, mainly due to the fact that is a in-memory data store, also possible to persist the data on file system.
It is open source and very well documented.
It is open source and very well documented.
What do you dislike about the product?
Does not have a query language.
It consumes a lot of RAM.
It consumes a lot of RAM.
What problems is the product solving and how is that benefiting you?
If the data fits on a key value pair, store it and retrieve data is very fast, this could be used as cache on top of other applications, or databases.
Redis great as K/V cache.
What do you like best about the product?
reliable and scalable: when working with a cluster (and if you have a proper sharding strategy), your DB can scale to a pretty high number and not die in the middle of any spike. Both the client and the command line tool are easy to use and well-documented.
What do you dislike about the product?
There's no GUI for managing the keys and values stored in REDIS. Lack of some basic permission, there should be a way of having a user with restricted commands (i.e: no keys, now write command, etc.).
What problems is the product solving and how is that benefiting you?
REDIS is used as chance storage in our data visualization application where responsive time is key . This in-memory database helped to solve many of the use cases we've had with our product like user-based caching and real-time analytics.
Best for storing sessions.
What do you like best about the product?
I always prefer Redis because it's so convenient and helpful when it comes to storing sessions. Redis stores data in memory so that reading and writing data using Redis is the fastest so the website's performance is enhanced. and the major benefit of using it is that I don't have to write so many lines of code.
What do you dislike about the product?
I don't dislike anything about Redis, but it was not easy to use I had to debug my code so many times.
What problems is the product solving and how is that benefiting you?
I started using Redis because we wanted our website to work faster our website was working properly but it was working slowly after storing some cookies and sessions so Redis came for the save and after that day I always used Redis for storing any key-value pair type of data.
Used Radis for Cache Implementation
What do you like best about the product?
I used redis in my project for implementing the cache mechanism. it is very fast and reliable.
Also like the redis command line (redis cli) easy to add, remove and update the value in the redis server.
Also like the redis command line (redis cli) easy to add, remove and update the value in the redis server.
What do you dislike about the product?
In redis command line when we start writing any command it will not give any suggestions or automatically fill the command like other cli tools we can use tab button it will automatically fill the remaining command.
What problems is the product solving and how is that benefiting you?
I have designed the cache mechanism using the redis. Whenever someone hits the API for the first time the response I am storing int the redis server. And next time when user hit the API with the same data the response will get return from the redis itself.
It save the extra https calls and improved the performance of the whole application.
It save the extra https calls and improved the performance of the whole application.
Recommendations to others considering the product:
You can use redis as a caching server or it also work very good as no SQL database.
The Best In-Memory Database for Cache
What do you like best about the product?
Speed !!, as Redis is an in-memory DB, it is very fast, which is its USP. It is very simple to use, just need to insert data in a key-value format, and it will work. Redis can also be used primary database but I have used it as caching only. the key-value read operation is very fast probably in a few milliseconds.
What do you dislike about the product?
very few apps where you don't dislike anything, Redis is one of them, I am using Redis for the last 2 years, yet found nothing to dislike. In the case of a large value, it may take a few extra milliseconds to process.
What problems is the product solving and how is that benefiting you?
We are using it as cache, and it has brought down our response time by 10 times, as compared to DB call. We have used the hash operation also, which is again an excellent function from Redis. We have a requirement for TTL in our documentation, with Redis we are able to handle that too with ease.
best caching in memory DB
What do you like best about the product?
too much lightweight with API interaction
support in AWS and many other clouds services
support many types of data types to match use case of many caching scenarios
support in AWS and many other clouds services
support many types of data types to match use case of many caching scenarios
What do you dislike about the product?
Single thread nature hang sometimes on many request
Not reliable for real time DB due to lack of session handling
Documentation is not proper to understand deeply
Not reliable for real time DB due to lack of session handling
Documentation is not proper to understand deeply
What problems is the product solving and how is that benefiting you?
in memory caching
Remote Dictionary Server
What do you like best about the product?
Fast read and write
Clustering and Distributing between servers
A lot of variation in data types.
Clustering and Distributing between servers
A lot of variation in data types.
What do you dislike about the product?
Single-Threaded. You won't benefit from having multi-core CPUs.
Lack of documentation; debugging can be onerous
Lack of documentation; debugging can be onerous
What problems is the product solving and how is that benefiting you?
I am solving caching-related problems with Redis.
user sessions handling, much easier than using a relational database to do it
user sessions handling, much easier than using a relational database to do it
showing 11 - 20