Sign in
Sign in
or
Create a new account
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Redis

Jetware | 170715-redis_4_0_0

Reviews from AWS Marketplace

0 AWS reviews
  • 5 star
    0
  • 4 star
    0
  • 3 star
    0
  • 2 star
    0
  • 1 star
    0

External reviews

74 reviews
from G2

External reviews are not included in the AWS star rating for the product.

    chedi t.

redis review

  • April 23, 2016
  • Review verified by G2

What do you like best about the product?
Redis as a key/value network storage database gives exactly what it advertises. the In memory storage can really boost the performance of many application while relieving the developer of the headache of managing shared memory between threads or programs on the same machine or over network.

With the increasing reliability of the hardware, we are unlikely to have a server failure that will cause the loss of the data and even if that is an issue, with the persistent storage and the data replication between servers you can have a robust system that will keep your data with little to no overhead
What do you dislike about the product?
nothing in particular, redis is a very reliable product that do one thing and do it right
What problems is the product solving and how is that benefiting you?
We started using redis as a cache system for Django, but with passing time we started using it directly in to share data between various applications and systems.
Recommendations to others considering the product:
Redis is a great tool for storing key value data, don't use it a relational database and adapt your software to redis and not the other way around to get the most of it.

    Prashanth G S.

Used as a cache between DB and application

  • July 25, 2015
  • Review provided by G2

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

    Internet

Great experience with Redis

  • July 22, 2015
  • Review verified by G2

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.

    b h.

Solid product with some limitations

  • July 16, 2015
  • Review provided by G2

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 71 - 74