Redis: A Caching Database on Steroids
May 24, 2016

Redis: A Caching Database on Steroids

Adam Lauer | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Redis

We use redis as a cheap, available, quick storage option. Think of it as a cache on steroids. It lets us store mass amounts of data and access it quickly. The best part is the access cost is not per demand, you are just paying what is hosting the redis clusters.
  • Quick lookup/interaction with data
  • Excellent key-value storage where everything is treated as a hashtable
  • Cheap alternative to other storage solutions
  • Mass amounts of storage is supported
  • The backup and recovery solutions are not ideal; recommend backing it with a more durable option
  • The spin up to find an optimal setup for performance takes time and testing
  • No super user friendly GUI application to interact with the data
  • One implementation of Redis saved our company thousands of dollars a month in data storage by switch to redis
  • We were able to increase our performance and scale the system to millions of users without drastically increasing costs
  • We had to accept possible loss of data during a backup/recovery situation, so data was not critical
Redis is had higher performance at a cheaper cost than any of these alternatives. The downside is the data is not as durable as these alternatives. Redis is like SQL where you pay of the instance running 24/7 where dynamo and s3 you pay per usage. Redis schema most closely resembles dynamo where it is a flat table, but even more simple with basically a hashkey-value system with just query lookups. We selected redis for the speed and cost and were able to store and access our data in such a way we only needed the query system.
The ROI has been phenomenal and we plan to extend our usage.
This is best for needing to access data at a high volume quickly at a low cost. This is not the best option if you need high durability of the data and cannot suffer any data loss. Redis is perfect for key-value situations of data including a key being a hash and the value being a huge json object. It is not good when you need a more relational schema.