Easy enterprise caching with Redis
March 22, 2019

Easy enterprise caching with Redis

victor pease solano | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Overall Satisfaction with Redis

We used to have most of our web apps accessing our database backend directly, and this was very resource consuming, especially in catalogs and details. This was more critical in our e-commerce storefront. With Redis, we were able to update our webs in order to cache all the queries with resources displayed frequently. In that way, we freed our servers of a huge load. The auto-expire function lets us use the Redis cache and not have to continuously monitor it.
  • It's an incredibly fast database with restrictions. It only has key-value combinations but good anyway.
  • For caching, at the first request-> write to the cache and read from it since DB query is expensive.
  • Persistence, It's like having your session active any time you want.
  • Software-based so the high availability configuration is a little bit tricky.
  • The expire function is manually managed, so keep all your variables well documented.
  • Better to create a Proxy service to deal with Redis values in order to isolate your app from the complexity (not too much anyway).
  • Positive: we used recycled hw for Redis and it worked just perfect because we had a lot of memory there.
  • Positive: web experience increased because dynamic content is cached.
  • Negative: migration to the cloud is not as smooth because features, such as data persistence, can be expensive.
  • Analyst Reports
  • Third-party Reviews
it was clear from the very beginning that we need to free up the DB and we decide to go for a key-value database with a blazingly fast performance so we started to look for the leader of the market and it was Redis by far, something that we have proven during tests and in production.
One key feature: easy to use. you can install and use it under minutes. For the rest of the options, you have to do more configuration and settings. Besides all these, Redis is in-memory so the performance is a blast. Considering that simple is better, the proof of the concept was easy and smooth.
Redis is a specialized key-value store, so it's best suited for session variables storage and cache'ing. Redis helps you identify database queries that are repeated exactly the same (for instance, combo lists, product catalogs, configurations, etc).

Redis is atomic, that means you don't have to deal with variables to being blocked to ensure concurrency. So it's great for dashboards, leaderboards, and apps like that.

Redis is not a common database, so don't use it as your repository for data entry or visualization. Yes, it's fast but not that way.

Redis™* Feature Ratings

Performance
8
Availability
8
Concurrency
9
Scalability
7
Deployment model flexibility
6