Progressive delivery
Blue-green, canary analysis, a one-box region and feature flags composed into a release path where a bad deploy is a non-event.
What this design does
Deploying and releasing are different verbs here. Code deploys to green while blue serves; a one-box slice bakes the build before any real wave; the canary takes 5% of traffic plus a mirror of blue's, and automated analysis compares their golden signals — a regression rolls back weights without a human awake. Feature flags then release functionality gradually, independent of the binary. The result: shipping on Friday stops being brave.
The patterns it composes
- Blue-green deployment — two identical stacks; release = flipping traffic weights, rollback = flipping back
- Canary + automated analysis — 5% of traffic, judged on golden signals against the baseline — promotion is earned
- One-box / canary region — wave 0 is a single box that bakes for hours before the fleet sees the build
- Traffic mirroring — green also receives a copy of blue's real traffic — bugs surface with zero user exposure
- Feature flags — deploy the code dark, release the feature later, kill it in seconds if needed
Import it, attach your own numbers, and verify the design against failures — or read the engineering notes.