Progressive delivery and canaries
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
limit the blast radius of a change by exposing it gradually.
Planned topics
- Progressive delivery: release to a small share of traffic, watch, then widen (for example 1%, 10%, 50%, 100%).
- Canary: a small group running the new version beside the old one, compared on the same traffic.
- Feature flags separate deploy (code present) from release (behavior on); both can be staged.
- Choose the canary population with care: representative traffic, enough volume to detect a difference, and a clear bake time per stage.
Draft outline details
Demonstration
Rollout plan table: stage | traffic | bake time | metrics compared | promote rule. Mention tools by role (service mesh or ingress weights, a rollout controller, a flag service); verify tool versions before recording.
Check your understanding
What is the difference between deploying and releasing with a feature flag?
Show answer
Deploy puts the code in production; release turns the behavior on for users.
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.