Why Redbus Skipped Valkey and Bet on a New Cache Architecture

Redbus, a leading travel ticketing platform, transitioned its distributed caching system from AWS ElastiCache to Dragonfly to reduce costs and enhance efficiency. The move was prompted by changes in the Redis license and the emergence of Valkey as a successor fork. However, Redbus sought to explore alternatives that could provide more substantial performance and scalability improvements. Dragonfly's architecture, which uses a thread-per-core, shared-nothing design, appealed to Redbus due to its ability to overcome Redis's single-threaded limitations. Benchmarks demonstrated Dragonfly's superior performance in throughput, latency, and memory efficiency compared to both Redis and Valkey, leading to a decision to adopt Dragonfly Cloud for production deployment. This choice enabled Redbus to focus on its core business without the operational burden of managing new infrastructure, achieving a significant reduction in caching costs and improved hardware utilization across its services. The experience underscored the importance of using forced migrations as opportunities to reevaluate and optimize system architectures for better performance and cost efficiency.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.