deployment and release
Two separate decisions: deployment puts a new version on the infrastructure, release decides which users actually get it.
In more detail
Separating them lets code ship dark and be exposed gradually, for example by a canary or a feature flag. A rollback of a release can then be a traffic or flag change rather than a redeploy.
Related terms
- release strategy — A plan for how a new version reaches users over time, such as rolling, blue-green, canary or feature flags.
- feature flag — A switch in the code, controlled from outside, that turns a feature on or off for chosen users without a new deployment.
- canary release — Sending a small share of real traffic to a new version first, and increasing it only while its metrics stay healthy.
- software deployment — Putting a specific version of software into an environment, such as staging or production, so that it runs there.
- release — Making a version of software, or one of its behaviours, available to users; also the versioned package being made available.
- kill switch — A control, usually a feature flag, that turns a feature off immediately without a new deployment.
Taught in
- Introduction to Release Strategies — Continuous Integration & Continuous Delivery Pipelines
- Feature Flags and DORA Metrics — Continuous Integration & Continuous Delivery Pipelines
- Restoration: Failed Deployment Recovery Time — DevOps & Site Reliability Engineering
- Continuous Delivery Versus Continuous Deployment — DevOps & Site Reliability Engineering
- Decoupling Release From Deployment: Feature Flags — DevOps & Site Reliability Engineering