How teams scaled Redis: 3 real case studies
3 of the 73 engineering write-ups in our database mention Redis in their stack. They come from 3 companies (Shopify, Stack Overflow and Stripe) and were published between 2016 and 2026. 1 of the 3 state concrete scale numbers, for example "$5.1 million sales/minute (Black Friday 2025 peak)" (Shopify). Each card below links to our short summary and the original post.
We replaced Redis with MySQL for inventory reservations—and it scaled
Shopify moved checkout inventory reservations from Redis to MySQL using one row per sellable unit, a bounded pool of 1,000 rows per item/location and SELECT ... FOR UPDATE SKIP LOCKED. The real ceiling was connections held by other checkout code: tagging SQL by business process and measuring hold time in ProxySQL found it, and the cleanup removed 50% of reads and 33% of transactions on the primary.
Scaling your API with rate limiters
The four kinds of rate limiters and load shedders Stripe uses to protect its API.
Stack Overflow: The Architecture - 2016 Edition
A tour of how Stack Overflow serves a huge site from a small number of powerful servers with heavy caching.