Blue-Green Deployment
ELI5 — The Vibe Check
Blue-green deployment means running two identical production environments — Blue (current) and Green (new). You deploy the update to Green while Blue keeps serving users. Test Green thoroughly. Then flip the traffic from Blue to Green in one instant switch. If anything goes wrong? Flip back to Blue in seconds. Zero downtime. Instant rollback. It's the 'have a backup ready' deployment strategy.
Real Talk
Blue-green deployment is a release strategy that maintains two identical production environments. Only one (blue) serves live traffic while the other (green) receives the new deployment. After validation (smoke tests, health checks), traffic is switched from blue to green via load balancer, DNS, or router update. The previous environment remains available for instant rollback. While simple conceptually, it requires managing database migrations carefully and doubles infrastructure costs temporarily.
When You'll Hear This
"Do a blue-green deploy for the database migration — we need instant rollback capability." / "The DNS switch from blue to green took 30 seconds — zero downtime."
Related Terms
Canary Release
A canary release is like sending a canary into a coal mine — you deploy the new version to a tiny fraction of users first and watch closely.
Deployment
A deployment is the event of pushing your code live — it's both the action and the thing you deployed.
Load Balancer
A load balancer is like a traffic cop for servers.
Rolling Update
A Rolling Update is when you update your app one server at a time instead of all at once.