Pattern 50 / OPS

Canary Deployment

Use this when reducing deployment risk by exposing new code gradually.

Pressure
Reducing deployment risk by exposing new code gradually
Mechanism
Send a small percentage of traffic to the new version, monitor, then expand or roll back
Toll
Requires traffic splitting, compatible versions, and strong metrics
Architecture plate50
Diagram for Canary Deployment
Executive brief

Canary Deployment fits when reducing deployment risk by exposing new code gradually. Mechanism: send a small percentage of traffic to the new version, monitor, then expand or roll back. Use it for production releases where real traffic catches issues tests miss. The toll: requires traffic splitting, compatible versions, and strong metrics.

Use when

Production releases where real traffic catches issues tests miss.

Example

1% of requests hit vnext before ramping to 25%, 50%, 100%.

Review framing

Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.

Same pressure family

Observability and Operations Patterns

48Health Check Endpoint49Distributed Tracing
← 4951 →