Deployment strategies
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
release with low risk and automatic rollback.
Planned topics
- Rolling: replace pods gradually; needs readiness probes and backward-compatible changes.
- Blue-green: run the new version beside the old, switch traffic at once, switch back to roll back.
- Canary: send a small share of traffic first and compare error rate and latency.
- Automated rollback triggers on failed health checks or SLO burn; the database must be compatible with both versions (expand then contract).
- Tools: Kubernetes Deployments, Argo Rollouts, or Flagger; verify versions before recording.
Draft outline details
Demonstration
a table comparing the three by speed of rollback, resource cost, and risk exposure.
Check your understanding
What must be true of the database for a safe rollback?
Show answer
The schema must work with both old and new code.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.