release strategy
A plan for how a new version reaches users over time, such as rolling, blue-green, canary or feature flags.
In more detail
Each strategy has a traffic shape, a signal that permits the next step and a rollback mechanism. Choose by the failure you can detect and the rollback you can execute under pressure.
Related terms
- rolling update — Replacing instances of an application with the new version a few at a time while the rest keep serving.
- blue-green deployment — Running two complete environments, blue for the current release and green for the candidate, and switching traffic between them in one step.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- feature flag — A switch in the code, controlled from outside, that turns a feature on or off for chosen users without a new deployment.
Taught in
- Introduction to Release Strategies — Continuous Integration & Continuous Delivery Pipelines
- Rolling Updates and Rollbacks — Continuous Integration & Continuous Delivery Pipelines
- Blue-Green Deployments — Continuous Integration & Continuous Delivery Pipelines
- Canary Releases — Continuous Integration & Continuous Delivery Pipelines