External reviews
External reviews are not included in the AWS star rating for the product.
A Good Distributing in Memory Caching Service
What do you like best about the product?
A lot of variation in data types.
Perfect for read-intensive applications.
Supports many programming languages.
The replication feature is very useful.
Perfect for read-intensive applications.
Supports many programming languages.
The replication feature is very useful.
What do you dislike about the product?
Sometimes the documentation is very clear
The data querying could be improved
The data querying could be improved
What problems is the product solving and how is that benefiting you?
We solved many problems such as
- Sharing of cache between multiple microservices
- We usually put the data read-intensive records in the cache for example the tending news for news website
- Sharing of cache between multiple microservices
- We usually put the data read-intensive records in the cache for example the tending news for news website
- Leave a Comment |
- Mark review as helpful
Best Cache store
What do you like best about the product?
We used it save the reservation data in cache for faster ii experience.
What do you dislike about the product?
There is nothing which I disliked as of now.
What problems is the product solving and how is that benefiting you?
Slow read from rdbms where caching the reservation data helps in quick response time.
Scaled our Php Systems 100x and turned a 1 hour lag ELK cluster into realtime.
What do you like best about the product?
Its an all in one Utility Pack that uses very little memory on startup. I have used it for storing XML hotel master data as Tables rows. While caching inventory as Key/Values and as a Broker to improve performance for the ELK stack. The distributed cache makes it even faster when using multiple data-centers across continents.
What do you dislike about the product?
It has a very old pre-compiled version for Windows.
What problems is the product solving and how is that benefiting you?
Our greatest challenge was Session replication & Session storage for our LAMP Php websites. We were subject to use sticky session based Load-balancing, but as soon as we realized Redis can store Php sessions, we started focusing on development instead of platform scaling. We increased our site/hits by 100x times and sales by 10x within a short period. We also used Redis as a broker for the ELK stack to reduce lag time to almost realtime.
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.
Very Fast Caching System
What do you like best about the product?
Very easy to install
Great CLI
Great Queries
Multilanguage support
Integration with AWS
Great CLI
Great Queries
Multilanguage support
Integration with AWS
What do you dislike about the product?
Bad experience with Windows since I am a Windows user.
A bit expensive.
Gets complicated when using clustering.
A bit expensive.
Gets complicated when using clustering.
What problems is the product solving and how is that benefiting you?
I mainly use for caching. I used it with machine learning with great benefits. A backend service runs and computes key data values for each customer and saves it in the cache. The front end user just subscribes to the values and sees live results.
used both redis cache and redis message broker and both are awesome.
What do you like best about the product?
perfect for shared memory, pub/sub is amazing as messaging broker.
What do you dislike about the product?
nothing to dislike actually , it is the best
What problems is the product solving and how is that benefiting you?
clearing cache for multiple microservices, with a subscribe event to the message broker.
shared caching for multiple microservices as well.
keeping data saved as persistent volumes due to microservices shutdown.
shared caching for multiple microservices as well.
keeping data saved as persistent volumes due to microservices shutdown.
Optimal In Memory Store
What do you like best about the product?
The flexibility of using it with many programming languages.
What do you dislike about the product?
The lack of UI client
Working in Windows in a pain
Lack of good tutorials and documentation
Working in Windows in a pain
Lack of good tutorials and documentation
What problems is the product solving and how is that benefiting you?
Mainly caching. Pre computing tasks that are required on each API call and save it in the cache. No need to compute if the data is already available in the cache. Saves so much time and CPU consumption.
My Experience of Using Redis
What do you like best about the product?
I can use redis to trigger event based actions in almost real-time. It's lightweight and easy to install on our server. The key-value data is simple too, suitable for simple use like an event parameters or something like that
What do you dislike about the product?
Its reliability is not as good as others. I've got several disconnected events and its not because of network connection. I've debugging it, and the problem is from the redis connection lost without a reason. and when i want to debug its value using Redis Commander its not as friendly as the others
What problems is the product solving and how is that benefiting you?
I can create a queue too using redis with the help of a plugin (bee-queue). I can send a trigger to another platform on-the-fly after some event triggered. So i can make my action more reactive and real time too.
Recommendations to others considering the product:
Redis is lightweight, powerful, and fast for in-memory database. If you're using it right, it will be give your platform a big boost in performance.
I can use it to trigger another event in another platform in almost realtime. But take cautions, sometime i got Redis Connection lost without any reason (and its not network problem)
I can use it to trigger another event in another platform in almost realtime. But take cautions, sometime i got Redis Connection lost without any reason (and its not network problem)
An amazing tool to keep data for cash, and also use as pub/sub mechanism
What do you like best about the product?
Mostly that I like is speed to reading and writing key->value data to Redis, It's a very convenient tool to use as a cashing mechanism.
Also, I like the pub/sub mechanism to use it for communication betwin microservices.
Also, I like the pub/sub mechanism to use it for communication betwin microservices.
What do you dislike about the product?
The only thing that I dislike, is some issues with do querying and to get data with some data with needed conditions
What problems is the product solving and how is that benefiting you?
Mostly the cashing problems, and to keep the data that should be written and read fast and, for don't store them to that main database.
Recommendations to others considering the product:
If you want to start using microservices for enhancing your product it will a good idea to use Redis as a message broker.
Redis helped us in reduce the DB load, increasing the ability to serve more users at the same time
What do you like best about the product?
Redis is simple to implement yet super efficient.
What do you dislike about the product?
I don't have any subject I don't like about Redis.
What problems is the product solving and how is that benefiting you?
We have a heavy loaded DB , in our pick hours we get 20K hits/s. Redis alllows us to keep it fast and readable.
showing 31 - 40