Redis: More than just cache
April 10, 2019

Redis: More than just cache

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Redis

Redis is used as a cache layer for our high read data as well as a database layer for write-intensive data. It's used in the entire engineering department as the de-facto caching layer for all services being built. The read and write speeds are unmatched because of the simplicity of the design.
  • Simple Key Value storage
  • Easy interface compared to other databases
  • Reliable performance characteristics
  • Redis needs better distributed support. I know this is not the point, but a distributed Redis with some CAP tradeoffs would be useful
  • Redis should be more clear on its pooling capabilities. Should you use a pool or just use a single connection?
  • It would be nice if Redis had a better CLI
  • More throughput
  • Less database resources used
  • Improved latency
  • Product Features
  • Product Usability
  • Product Reputation
  • Prior Experience with the Product
Memcached is the closest to Redis because it is also a key value in-memory storage solution. The reason to go with Redis is for its more useful datatypes, pubsub, and much bigger value storage.
Good for key value storage. Simple as that. If you need something that has relational data or need more complex data structures, don't use Redis.
If you need something that can be written and read by multiple services, that is as fast as possible, use Redis. The simplicity is its biggest strength, and making it more complex will just ruin the product.

Redis™* Feature Ratings

Data model flexibility
Deployment model flexibility