All visualizationsSystem Design · 14 of 34
Blue-Green vs Canary — two ways to ship without burning users
One flips ALL traffic and can flip it back in seconds; the other lets 5% of users breathe the new version first.
💡
THE BIG IDEA
Every deployment is a bet placed with your users’ afternoon. Blue-green bets big and keeps an instant undo button: two identical environments, one switch. Canary bets small and watches: 5% first, metrics compared live, widen only while healthy. This theatre runs BOTH — including the day the release is broken, so you can compare blast radii instead of slogans.
Press ▶ Play to watch it run step by step, or use the arrow buttons to go at your own pace.
1
Friday, 4pm. Everyone is on v1, served by the BLUE environment. v2 is ready — and the question every team eventually answers badly once: how do we ship it without burning our users?
Two disciplined answers exist. Both begin the same way: the new version starts life serving NOBODY.
👥Your users
🚦Traffic switch (router/LB)
🟦BLUE — v1 (live)100% of traffic
🗄️One database
handling requestjust addedunder loadDOWN
1/11
UP NEXT IN SYSTEM DESIGN
Design WhatsApp (Chat at Scale)
Persistent connections, a presence router, and durable offline delivery
The Consistent-Hashing RingDesign WhatsApp (Chat at Scale)