REDIS great as K/V cache
Updated February 18, 2020

REDIS great as K/V cache

Anson Abraham | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Redis

[It's being used as a] Caching service for quick key lookups.
  • Quick key lookups.
  • Distribution of data is easy and reliable.
  • Almost HA.
  • HA automatic failover for master and promoting slave on own.
  • Doesn't handle 1M r/s sadly.
  • Cross DC replication not so great.
  • Reduced need for high end DBservers.
  • Better than memcacheD.
  • Doesn't do well for time series data though, which sucks.
  • Redis vs. Aerospike ... Aerospike is way BETTER. But very expensive.
  • Between Redis and MemCacheD, Redis outright is better than it.
  • Couchbase is better than Redis, but CouchB is expensive
  • Cockroach is really nice, but still kind of relatively new compared to redis.
  • rethinkDB is comparatively better than redis. But misses out on geolocational info which redis supports.
If it's open source, then Redis. Though now RethinkDB and Riak are going full on opensource. and being supported by community. So might give those a re-try as well.
If you're doing caching, it's perfect. Especially when doing key-value store lookups. However, if you have a hardware load balancer, then setting up multiple slaves would be good. One slave is not so great for 1 million reads per sec. Transactions to the master can be slow at times depending on how much written to it Not as afast as say cassandra for writes.