Skip to main content
PreparationZone Logo
PrepZone

Rolling Updates, Rollbacks, and Probes

maxSurge, maxUnavailable, readiness/liveness probes, and instant rollback.

Pass checkpoint below

Why this matters

  • This topic directly affects how reliably BookStore reaches production — rolling updates and rollbacks change bookstore versions with bounded blast radius..
  • Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
  • Later modules assume you can explain both the why and the concrete file or command involved.
  • Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
Rolling
v1.0 pods3 running
v1.1 pod addedOne at a time
v1.0 pods removedZero downtime
Blue/Green
Blue (v1.0)Live traffic
Green (v1.1)Validated, idle
Switch trafficInstant cutover
Rolling replaces pods gradually. Blue/green switches traffic between two full environments.

maxSurge and maxUnavailable

Surge without downtime: BookStore engineers treat this as part of the standard path from laptop to rolling updates rollbacks readiness. Document decisions in the team runbook so on-call knows which knobs exist.

Key ideas

  • maxSurge and maxUnavailable — primary idea for rolling-updates-rollbacks
  • BookStore context — catalog API, checkout, and inventory services share the same pattern
  • Automation — prefer pipeline jobs over manual SSH steps
  • Verification — staging must prove the change before prod traffic

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Instant rollback
  • Production checklist

Test yourself

Answer these before moving on — recall is what makes it stick.