Redis Cloud - Annual
RedisExternal reviews
94 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Simplicity is Beauty and Beauty is simplicity.
What do you like best about the product?
The performance , robustness , easy to learn and ease to use in production environments .
What do you dislike about the product?
scripting language , i prefer that use javascript for scripting in redis .
What problems is the product solving and how is that benefiting you?
we are using redis in data caching and socket.io related using .
Recommendations to others considering the product:
support javascript as scripting language and connecting and integrating to another databases as an optional module .
Great in-memory storage
What do you like best about the product?
What's best to appreciate about Redis is how quickly it's growing since it's first appearance and how useful and fast it is for many parts of a software implementation.
It always seemed to me like a storage option for caching or indexing, but it is way more than that. Some features are definitely to be highlighted like:
* Pub/Sub message system.
* Redis Cluster
* Expires
* Lua scripting
* Blazing fast
Are some of the things I noticed that make a difference when looking for this kind of memory storage.
It always seemed to me like a storage option for caching or indexing, but it is way more than that. Some features are definitely to be highlighted like:
* Pub/Sub message system.
* Redis Cluster
* Expires
* Lua scripting
* Blazing fast
Are some of the things I noticed that make a difference when looking for this kind of memory storage.
What do you dislike about the product?
I used to dislike the lack of features on Redis, but that was like 2 years ago, it has grown so quickly so fast that it's scary, the community is strongly focus on this product development.
What problems is the product solving and how is that benefiting you?
Pretty much anything that needs to be stored and retrieved fast, like caching is a great use case for Redis. For example to store session information in web applications. Also to store large amounts of incremental and volatile data, since it can be "expired".
Recommendations to others considering the product:
If considering using Redis for a project, just try it, it's easy to use and feature-rich. The community is really active and there's no lack on tutorial for a lot of use cases.
Fast access to data
What do you like best about the product?
Simple and fast access to key/value data, as well as score and rank system.
What do you dislike about the product?
Not so easy to find/list existing keys. On the order hand, if you need list keys, probably you are doing something wrong.
What problems is the product solving and how is that benefiting you?
Cache, temporarily data, message queue, non persistent data, in memory database.
Easy to use. But too expensive. Memory limited
What do you like best about the product?
Very easy to use. A novice can pick it up and put to use almost immediately. Documentation very easily done
What do you dislike about the product?
Very expensive, because of memory limitation. Not sure if the current version supports multiple instances
What problems is the product solving and how is that benefiting you?
I needed a database that offers very fast read and write operations. Redis delivered. Except that my needs have outgrown now
Recommendations to others considering the product:
It's really the Swiss army knife. Documentation is a breeze to pick up. Really! Performance is as advertised.
Used as a cache between DB and application
What do you like best about the product?
The data structure in Redis are very helpful. The set operations helped in efficiently organizing the data and less operation needed from our end. We maintained all the Database relationship in Redis for faster access.
What do you dislike about the product?
No operation on the keys can be performed. Like sorting list based on key. There is a work around, which didn't perfectly fit well
What problems is the product solving and how is that benefiting you?
The main problem was to make the client as light as possible. Fetching data from DB was really slow for our flask application. So we thought Redis was the way to go. Where all the data are cached with drastically reduced the REST response time.
Recommendations to others considering the product:
Easily to use. Can build a prototype in a week(depends on what you want to do). Highly recommend to use
Great experience with Redis
What do you like best about the product?
Super fast response times (main purpose of redis)
What do you dislike about the product?
Data is stored in memory (needed for the quick retrieval of the data). This is generally not an issue, however very large datasets (> 250 GB) can't be fully stored in the memory and redis might not the best option for very large sets.
What problems is the product solving and how is that benefiting you?
Fast retrieval of product recommendations. Normal SQL requests take too long with larger datasets. Redis requires that the data is organized differently, but the extra work upfront pays off with every data request.
Solid product with some limitations
What do you like best about the product?
Small feature set, predictable performance, auto-expiry of data, very fast, very simple text based protocol, simple administration, easy to understand where your data is and what's happening to it.
What do you dislike about the product?
I can't say I was enormously pleased when they introduced Lua scripting. The main selling point of the data store was it's simplicity and predictable performance. It would have been preferable that a couple more commands be implemented in C rather than bring stored procedures into the mix. That choice was probably based more on product development than customer need, and again the main attraction was the premise of simplicity. In fairness, it's been a couple of years since I last used it in production so perhaps it's worked out really well since then.
What problems is the product solving and how is that benefiting you?
I've used it for auto-expiring caches, it's great for that particular use-case. Can also be used as a convenient buffer for batch processes. I wouldn't put anything into Redis that I couldn't afford to lose, I guess it's more like memcached in that respect.
Recommendations to others considering the product:
Why not give it a try? It's simple enough that you can get it running in 10 minutes. The basic commands don't take a lot longer to master, and there's some advanced stuff you can do later. I would consider it ideal for transient data storage.
showing 41 - 47