A canary deployment reduces the impact of production bugs by separating deployment—running an updated component in production—from release—routing traffic to it. The updated component runs alongside the current version and initially receives only a small share of traffic. section 5.5.2 section 5.5.2
A progressive rollout proceeds by:
- Increasing the share of traffic routed to the updated component until it handles all traffic. section 5.5.2
- Using telemetry from the updated component to detect problems; roll back if it indicates failure. section 5.5.2
Canaries help limit user disruption, but some strategies start the application twice, slowing deployment. Evaluate the trade-off against the risk of exposing users to a faulty update. section 5.5.2 section 6.1.2










