Why this matters
- This topic directly affects how reliably BookStore reaches production — deployment strategy chooses how bookstore replaces running versions.
- 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 and blue/green
Risk vs cost: BookStore engineers treat this as part of the standard path from laptop to deployment strategies readiness. Document decisions in the team runbook so on-call knows which knobs exist.
Key ideas
- Rolling and blue/green — primary idea for deployment-strategies
- 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
- Canary for BookStore
- Production checklist
Test yourself
Answer these before moving on — recall is what makes it stick.