Atlas › 16 CI/CD Pipelines › Deployment Strategies☰ Read as one page
Deployment Strategies
6.1Where Tests Fit in DeploymentDeployment is the moment tests face reality. Different deployment strategies create different risk profiles, and each demands a different…6.2Blue-Green DeploymentTwo identical environments exist: blue (current production) and green (new version). The new version is deployed to green. Once validated…6.3Canary DeploymentThe new version is deployed to a small subset of servers (the "canary"). A small percentage of real traffic (typically 1-5%) is routed to…6.4Rolling DeploymentInstances are updated one at a time (or in small batches) across the fleet. At any given moment during the rollout, some instances run the…6.5Strategy Comparison6.6Feature Flags as a Testing StrategyFeature flags decouple deployment from release. You deploy the code but keep new features hidden behind flags, then enable them gradually.6.7Testing the Deployment Pipeline ItselfThe deployment pipeline is software. It can have bugs. Test it.6.8Hands-On Exercise1. Identify which deployment strategy your team uses. If you do not know, ask your DevOps/platform team. 2. Map out where tests currently…