Canary Deployment
ELI5 — The Vibe Check
Canary deployment is releasing your new code to a tiny percentage of users first to see if it explodes. Just like miners used canaries to detect gas — if the canary dies, stop going deeper. You roll out to 1% of traffic. If error rates stay flat, go to 10%, then 50%, then 100%. If anything breaks, only 1% of users noticed and you can roll back instantly.
Real Talk
Canary deployment is a release strategy where new code is gradually rolled out to an increasing percentage of users/traffic while monitoring key metrics (error rates, latency, business KPIs). If degradation is detected, traffic is routed back to the stable version. It combines the safety of staged rollouts with the speed of continuous deployment, minimizing blast radius of potential issues.
When You'll Hear This
"We canary the release to 5% of traffic for 30 minutes before going wide." / "The canary caught a memory leak that only appeared under production load."
Related Terms
Blue-Green Deployment
Blue-Green Deployment is like having two identical restaurants — one is open (blue), and you're setting up the other (green) with the new menu.
Feature Flag
A Feature Flag is an on/off switch for a feature in your app, controlled without redeploying. You ship the code but keep the feature hidden behind a flag.
Rollback
A rollback is the panic button. When you deploy something and it breaks production, you hit rollback and the system reverts to the last working version — l...
Rolling Update
A Rolling Update is when you update your app one server at a time instead of all at once.