External reviews

External reviews are not included in the AWS star rating for the product.
In memory distributed caching solution
What do you like best about the product?
- Various data structures are provided
- Lots of use cases like rate limiting or caching are provided out of the box
- Has good durability (AOF and snapshot)
- Easy to use
- Lots of use cases like rate limiting or caching are provided out of the box
- Has good durability (AOF and snapshot)
- Easy to use
What do you dislike about the product?
- Cluster management are harder to build and its Enterprise SaaS are expensive
What problems is the product solving and how is that benefiting you?
Redis helped us build caching mechanism easily, allowing more RPS to traditional databases.
- Leave a Comment |
- Mark review as helpful
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.
Best Key Storage
What do you like best about the product?
I can easily access its database using the command line interface and also starting it up is easy. Easily accessible Session keys it is the market leader for session keys in my point of view
What do you dislike about the product?
It has too many options regarding its starting kit for a new person to learn it, there are not many documentations available on it for internet, it would do some good if there could be some extensive documentation for its all basic features as well as advanced features
What problems is the product solving and how is that benefiting you?
i can easily store all fo my clients sessions key in one place saving precious file storage and using Redis server instead which reduced my AWS costs
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.
Speed up your app
What do you like best about the product?
Redis is highly stable, and when caching the data, it increases application speed by a considerable amount. It is highly reliable, easy to set up, widely used, and beginner-friendly. The community support is good.
What do you dislike about the product?
It does not support a variety of data types, so you'll have to do the conversion while writing and reading from it.
What problems is the product solving and how is that benefiting you?
We are increasing the speed of e-commerce app by caching different data leading to considerable improvement in User experience.
Best In-memory storage for fast data retrieval & caching
What do you like best about the product?
Redis provides in-memory database so it is very helpful to retrieve data faster & it can be used as caching also.
What do you dislike about the product?
It is in-memory database so it is not suitable to perform Relational actions like join & complex queries
What problems is the product solving and how is that benefiting you?
As of now we are using Redis to store cache data for social-media analytics
Cache for best redis
What do you like best about the product?
It is in a good position in terms of cache performance and usage in the market. The most ideal storage to store your keys and values.
What do you dislike about the product?
There is nothing I dislike about Redis in general. It is quite useful. There are many client leir and management tools connected by the software.
What problems is the product solving and how is that benefiting you?
Saving session keys for cache and session management with Redis. we used it for scenarios such as quick reading of config information at the start of our applications.
Best in-memory database experience
What do you like best about the product?
The speed and simplicity are amazing.
Easy to understand and implement.
Stores data in memory, therefore, can perform a huge number of read and write operations per second.
Easy to understand and implement.
Stores data in memory, therefore, can perform a huge number of read and write operations per second.
What do you dislike about the product?
If the system abruptly restarts, data is lost.
If we enable real-time data backup to disk in order to avoid the above issue, resource utilization skyrockets.
Also, logging makes things run slower.
If we enable real-time data backup to disk in order to avoid the above issue, resource utilization skyrockets.
Also, logging makes things run slower.
What problems is the product solving and how is that benefiting you?
We store a large number of key-value pairs in different fields.
These are updated in real-time so the live data is always updated and accurate.
These are updated in real-time so the live data is always updated and accurate.
showing 11 - 20