External reviews
External reviews are not included in the AWS star rating for the product.
Perfect Documentation
What do you like best about the product?
I use the Redis API in my python web-stack and it is one of the slickest things I have ever had the pleasure of working with. The application that I maintain, deepquill.com, needs to serve a high volume of requests while doing continuous cloud-resource tracking/management and it all has to happen asynchronously, so naturally I turned to Redis for a high speed caching solution. At the time I knew only Postgres and Redis works very differently, so I was new to the whole system. The solution I needed to implement with this database wasn't exactly trivial either, so I was prepared to spend a good amount of time slogging through source code to learn what I needed to alter to get this module to work how I wanted it to. -- To this day I have not seen a single line of it's source code -- It's all there in the documentation, written in plain English with examples and use-cases galore! Even if there were a faster and more reliable caching solution on the market (which there isn't) , I would honestly still pick Redis if only for it's thorough and accessible documentation.
What do you dislike about the product?
The only downside I could identify with this solution is that it is not really meant to store data in a persistent form. At least not by default. Redis does everything in volatile memory (which is why it can be so fast) , and while it is easy to set it up to write your data to disk from time to time (it's maybe 3 lines of code tops), it can potentially be confusing to people who come from a more traditional database and expect their data to still be there after a power cycle. The only people who would really suffer from this misunderstanding are those didn't read the manual though, so don't be one of those and you'll be fine. Just be warned: if you want Redis to record your data in a persistent form, you have to explicitly tell it to do that.
What problems is the product solving and how is that benefiting you?
I needed to keep track of user activity, resource utilization, message caching, and the status of many containers on many AWS EC2 instances with high time-resolution, and manipulate all of this data in such a way as to make it easy to tell when to do what with which resource (margins are slim so we want to be as efficient possible) Redis handles ALL of this for us and deals with asynchronous operations in a most sane and predictable way. Redis also lets us encrypt all of our data moving between layers, which is pretty badass in my opinion.
Recommendations to others considering the product:
If you are trying to control a secured Redis server using a shell script you want to use a "-a" flag followed by the password. This was the only thing I've found that wasn't explained in the documentation. But now you know!
- Leave a Comment |
- Mark review as helpful
Because Redis can minimalizes resource using Caching
What do you like best about the product?
Redis is best for caching, easy to set up, and easy to use. I'm still new with Redis, but I really like Redis because Redis is really helping me to cache data, I usually use Redis on Heroku or on my local machine, it's really easy to setup Redis on Heroku because you can just select from the Heroku features you need, and select the Redis features, it really helps me to deploy an app to Heroku using Redis.
What do you dislike about the product?
No, I really like Redis, I don't think that I disliked Redis
What problems is the product solving and how is that benefiting you?
API request faster if using Redis because our data is cached on Redis.
Recommendations to others considering the product:
I think we should start using Redis because with Redis you can cache your data, I usually use Redis on Heroku or on my local machine, it's really easy to setup Redis on Heroku because you can just select from the Heroku features you need, and select the Redis features, it really helps me to deploy an app to Heroku using Redis.
Robust and fast
What do you like best about the product?
Quick key lookups.
The data distribution is easy, robust and reliable&
The data distribution is easy, robust and reliable&
What do you dislike about the product?
If the instance goes down, there is no backup preserved. Single-threaded. Also a little expensive.
What problems is the product solving and how is that benefiting you?
Use it instead of cache.
Recommendations to others considering the product:
use it if you use other amazon products/aws
Faster and Reliable Yet OpenSource
What do you like best about the product?
Redis is one of my favorite databases. We have used Redis with NodeJS and Python. Due to its highly available nature, we used it in several areas like authentication & authorization, frequent HTTP response data caching, session management. We experienced that read/writes to Redis very faster, highly scalable, and reliable. Thanks to Redis Team to make it opensource so that we can use it freely.
What do you dislike about the product?
It would be really great if we can store key-file in Redis like we store key-value now.
What problems is the product solving and how is that benefiting you?
Data Caching, Active Sessions, Web Authentications
A fast and reliable data storage system.
What do you like best about the product?
It is a very fast and easy tool to implement, and also to configure the Redis services to our most peculiar environment that we want to give the service, highlighting that this system is highly compatible, since there are many tools that are based on this field of work in the software, determining that it is very flexible in understanding its subject matter, especially the developers who become familiar with this operational branch, while exercising a very guaranteed reliability.
What do you dislike about the product?
We can highlight that it contains some difficulties to scale Redis in a correct way in its entirety, making a point of reference that lately this software has become prohibitively expensive, since it exceeds the budget limits of many small category companies mostly, which contains a development process lower than other organizations, which cannot afford to pay these monthly payments, being an economic problem.
What problems is the product solving and how is that benefiting you?
We are currently using Redis to support distributed caching and synchronization in our application in a totally effective way in every sense, mentioning that our servers are operated on different systems, so ensuring that the entire infrastructure is well linked and that the key operations are atomic, it is very fundamental for us, to carry out complete and feasible jobs in any sense of visualization, offering us great performance and reliability.
Recommendations to others considering the product:
It is a great tool for highly distributed caching, on different servers, being used today by different categories of company sizes, from the small ones that can afford to pay its extensive price, to the largest and most significant development, which works much better when more tasks are integrated into the software, highlighting that Redis also works well for non-persistent data that does not grow over time.
Excellent solution for distributes cache
What do you like best about the product?
Redis is extremely stable and comes with a powerful community support, learning curve is easy .
What do you dislike about the product?
Nothing as such, working fine for our use cases and solving all infra problems,
What problems is the product solving and how is that benefiting you?
We have used Redis cluster to be used as a distributed cache solution and managing GBs of data with a minimal set of nodes.
Recommendations to others considering the product:
Redis provides a one stop solution for Enterprise applications, one must use it for distributed cache solution.
Data management tool
What do you like best about the product?
It is very easy to install redis, i used it in ubuntu server. The steps where very easy for installation.
What do you dislike about the product?
I was stucked with creating another instance on redis , the official documentation was not providing the information i needed.
What problems is the product solving and how is that benefiting you?
I used it with dot net core and ubuntu server for storing the data on redis, it stores the value in key value pair.
Easy to install, easy to use
What do you like best about the product?
Very easy to install, very easy to use, easy to connect to ELK stack (and that was my need)
What do you dislike about the product?
It is not so easy to create and manage cluster of Redis, it is easyer with other product (I choose Kafka in this case)
What problems is the product solving and how is that benefiting you?
Really easy to use inside an architecture with the ELK stack, expecially with LogStash as input and output
Fastest caching database for performance bootster
What do you like best about the product?
- Fast
- Multiple language driver support
- Pub / Sub feature
- Easy to store blob
- TTL can be specified
- Can reduce master database load drastically
- Multiple language driver support
- Pub / Sub feature
- Easy to store blob
- TTL can be specified
- Can reduce master database load drastically
What do you dislike about the product?
- Costly as service
- Can't store JSON directly, need to convert into string first, which is kind of tedious.
- I need a way to store JSON Directly
- Can't store JSON directly, need to convert into string first, which is kind of tedious.
- I need a way to store JSON Directly
What problems is the product solving and how is that benefiting you?
- Performance for storing cache'd data.
- Faster operations
- Faster operations
Recommendations to others considering the product:
- Faster insert and retrival, go for it.
Favourable for using with systems carring large set of data's and need instant modifications
What do you like best about the product?
It makes data interaction fast hence user can modify the data easily and can extract the latest set of data easily
What do you dislike about the product?
It's difficult to identify the stale data sometimes and need a lot of refresh or restart to get the proper results
What problems is the product solving and how is that benefiting you?
We save the data we extract from legacy systems and proviing the data to user to make modifications according to their need and then again feeding the data in legacy systems
showing 51 - 60