Last Minute Notes
  • Github
  • Docs
  • Learn
    @sayanstwt
Lessons
0/37 done
  • Timeouts, Retries & Breakers
  • Multi-Region Design
  • Cells & Shuffle Sharding
  • SLIs, SLOs & Error Budgets
  • Observability
  • Deployment Strategies
  • Backups & Disaster Recovery
Learn/System Design/Reliability & Operations

Deployment Strategies

7 min Intermediate 6 steps

Rolling, blue-green and canary releases with safe rollback.

Recreate
downtime
Rolling
gradual
Canary
smallest blast
v1v1v2UsersLoad balancerv1reqreq
request response data
In this lessonStep 1 of 6
  1. The problem
  2. Rolling
  3. Blue-green
  4. Canary
  5. Schema
  6. Recap
Step 1 / 6problem

Every release can break production

A new version might be slow, buggy or incompatible with the data.

The strategy decides how many users see a bad release and how fast you can undo it.

Key idea

Pick a strategy by rollback speed, risk and cost.

←→ step·R replay·Space pause

You'll learn

  • Rolling vs blue-green
  • How a canary catches a bad release
  • Expand, migrate, contract for database changes
  • Why config and data are deploys too
Read the full notesReliability and Operations, 3