Deployment strategies · Lesson 9 of 10 · 3 min read
Choosing a strategy
| Situation | Good choice | Why |
|---|---|---|
| Internal tool, brief downtime OK | Recreate or rolling | Simplicity |
| Typical stateless microservice | Rolling with readiness, preStop, maxUnavailable: 0 |
Cheap, safe enough |
| High-traffic, high-risk service (payments, checkout) | Canary with automated SLO analysis + flags | Smallest blast radius, objective gates |
| Need instant rollback, can afford capacity | Blue-green | Switch back in seconds |
| Versions can't coexist (exclusive locks, incompatible protocol) | Recreate (or blue-green with careful cutover) | No overlap |
| Big rewrite / new backend | Shadow traffic, then canary | Real-load testing without user impact |
| Product experiment | A/B test with flags | Decision-making, not safety |
| Mobile/SaaS with distinct customer groups | Rings | Progressive exposure by audience |
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.