Quick Notes138 words
Deployment strategies — quick notes
Deployment strategies — quick notes
| Pattern | Purpose |
|---|---|
| Blue-green | Two full-capacity environments; route to green at once or progressively; route back to blue |
| Canary | Small traffic slice first |
| Ring / progressive exposure | Widening audiences over time |
| A/B testing | Primary purpose: compare variants against outcome metrics, not rollout safety |
| Feature flags | Decouple release from deployment; kill switch |
Traps
- A/B testing offered as a risk-reduction answer — it is a product experiment.
- A traffic percentage alone does not distinguish canary from blue-green; check whether the design has parallel full-capacity pools.
blueGreen/ringedasstrategy:keywords — they do not exist. OnlyrunOnce,rolling,canary.- Fastest rollback for flagged code is turning the flag off, not redeploying.