Deployment places compiled binaries on production infrastructure; release is the separate business decision to expose a feature to users. Feature flags keep these steps independent by changing an application’s runtime path without recompiling or redeploying. section 13.3.4
Common rollout approaches make different tradeoffs:
- Rolling updates replace instances one at a time, keeping costs low but allowing different code versions to coexist. section 13.12
- Blue-green deployments keep parallel fleets for fast cutovers and rollbacks, at the cost of extra infrastructure. section 13.11 section 13.12
- Canary deployments send a small share of production requests to new code to limit the blast radius. section 13.12
Ship quietly, release when ready
An enterprise discount feature can be deployed with its flag off, then enabled for internal testers. When it is ready for users, flip the flag—no new deployment is needed. section 13.3.4
Figure 13.4 Separation of Concerns: Deployment is the technical operation of placing files on a server; Release is the business decision to expose those files to your users.

Use the diagram to distinguish placing files on a server from deciding to expose them to users. section 13.3.4




























