PATTERN Cited by 1 source

Canary deployment

Pattern

A canary deployment rolls out changes to a small percentage of users or infrastructure first, validates functionality and performance against health metrics, and only expands to full deployment after confirming safety at the initial scope.

Mechanism

1. Deploy the new version to a small subset (e.g., 1–5% of traffic or instances).
2. Monitor key metrics (error rates, latency, business KPIs) against baseline thresholds.
3. If metrics remain healthy through the soak period, progressively expand to larger percentages.
4. If metrics degrade, automatically roll back without full-fleet impact.

Connection to chaos engineering

The same progressive expansion principle underlies both canary deployments and progressive fault injection: limit blast radius by proving safety at small scale before expanding scope. AWS's resilience framework explicitly draws this analogy, using 1% → 5% → 10% → 25% scope expansion for chaos experiments mirroring canary rollout patterns (Source: sources/2026-06-22-aws-architecting-ai-powered-resilience-framework-on-aws).

Seen in

• sources/2026-06-22-aws-architecting-ai-powered-resilience-framework-on-aws — cited as the deployment strategy analog for progressive fault injection scope expansion