Skip to content

Deployments: blue/green, canary, flags and rollback

Ship changes without spending the error budget: size a canary's blast radius, plan rolling capacity, separate deploy from release with flags, and keep rollback safe.

30 min7 steps

By the end you can
  • Choose between rolling, blue/green and canary deployment for a change and its risks
  • Estimate how many users a bad canary affects before automated rollback
  • Choose a rolling-update batch size that keeps the fleet within its utilisation target
  • Use feature flags and expand/contract changes so a rollback never breaks data

Three ways to replace running code

Rolling

  • Replace in batches
  • Old and new side by side
  • Rollback = another rollout

Blue/green

  • Full new fleet, switch at router
  • Rollback in seconds
  • Pays for two fleets

Canary

  • Small share of real traffic
  • Compare metrics
  • Widen in stages with bake time
Combine them: canary one zone first, then widen in waves.

A change rewrites the pricing engine. Tests pass, but nobody is sure how it behaves on real traffic. You want to limit how many users a bug can reach. Which strategy fits best?

Answer this step to continue.