Super fast and easy to integrate
September 07, 2019
Super fast and easy to integrate
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Redis
We currently use Redis in only one core internal application, however, this application handles around 90% of our company's internet traffic. This application load balances requests intelligently across multiple downstream server clusters. Prior to this, we used to frequently run into bottlenecks at the DB layer when web server scaling alone was insufficient.
The great thing about this is also that each cluster can be running a different version of our application allowing us to maintain a high level of robustness for our larger enterprise customers, while also allowing us to deploy frequently to other clusters that want the bleeding edge. With Redis, being able to determine the right cluster for the right request happens blazing fast.
The great thing about this is also that each cluster can be running a different version of our application allowing us to maintain a high level of robustness for our larger enterprise customers, while also allowing us to deploy frequently to other clusters that want the bleeding edge. With Redis, being able to determine the right cluster for the right request happens blazing fast.
- FAST LOOKUPS. First and foremost, this is the bread and butter of Redis. It is our go-to for any highly performant lookups.
- SCALE OUT. Helps build distributed applications that need to share data across geographies.
- Better GUI clients. At the time of adoption, the choices for UI based clients were poor. Such tools are necessary for tier 1 support personnel who may not be entirely technically savvy.
- We use Redis for the purposes of routing data within our infrastructure. In this use case, we want there to be a little additional latency as possible. In this, Redis does a great job.
- Price
- Product Reputation
Industry adoption was the most important factors in deciding to go with Redis. The options really boiled down to a choice between Redis and Memcached. We tried both and found that support for Redis was far superior to Memcached in terms of hosting and maintenance. Redis was also gaining more traction in the dev community, so the choice became pretty clear.
We initially tried ElastiCache with Redis hosting. While it did the job of running Redis, we still had to deal with server sizing. We switched to Redis Cloud since that had auto-scaling and easy to use tools.