Redis is the backbone of our ephemeral data, from web page caching to session storage.
Anonymous | TrustRadius Reviewer
September 10, 2019

Redis is the backbone of our ephemeral data, from web page caching to session storage.

Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Redis

We use Redis to run frontend caching, sessions and backend value store systems for our main web property. We are big supporters of the community and love watching it evolve over time. We've been early adopters in the NoSQL movement starting with Mongo and Couch. We're still using Redis, although we can't say the same for the others.
  • Key value storage
  • Session and Cookie management
  • Frontend caching
  • Third-party library support sometimes lags
  • Weak type support
  • Everything is in memory, so you need lots of RAM
  • With Redis we can serve web pages must faster. Faster pages means better business.
  • Scaling across many servers we're able to support millions of visitors a month.
The ability for Redis to go really fast using in-memory storage has given us the ability to serve cached web pages blazingly fast. Beyond caching, we have been able to span across multiple servers to handle loads of millions of visitors to our websites. Although we only use it on one platform, the ability for it to be used across platforms is attractive.
Yes - We used memcached in the past for our cookies and sessions. Redis was the hot new thing, so we tried it out and realized all the hype was reality. Our needs were simple, we couldn't get memcached to span across servers. For web page caching, we used to use a homegrown system that would be stored on disk. Redis was in-memory, so that was obviously a much faster response time.
  • Price
  • Product Features
  • Product Reputation
Product reputation was a primary factor. We had heard about it, so it had a real organic grass-roots marketing hype behind it. But, what kept us is the ability for Redis to meet and exceed the hype. We were struck by its simplicity, speed and feature set. The price helped also, but it wasn't the main facotr.
We raved all the time about the application speed due to the performance gains we got initially from Redis. While we still actively use Redis, it's not something that often gets discussed. That's a good thing. It's rock-solid stability and performance has given us an advantage in website building and development.
We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.
Redis is well suited for front end caching of websites and apps. We also use it successfully to manage our web/app cookies and sessions. Everything in Redis is in your RAM, so if you need anything stored permanently you'll need to turn on the persistence options, which will slow down Redis a bunch since it has to write to disk.

Redis Feature Ratings

Performance
9
Availability
9
Concurrency
9
Security
7
Scalability
9
Data model flexibility
9
Deployment model flexibility
7