Library › Book 16 › Deployment Strategies -- Blue-Green, Canary, and Rolling
Deployment Strategies -- Blue-Green, Canary, and Rolling
7.1🔒Where Tests Fit in DeploymentDeployment is the moment tests face reality. Different deployment strategies create different risk profiles, and each demands a different…
7.2🔒Blue-Green DeploymentTwo identical environments exist: blue (current production) and green (new version). The new version is deployed to green. Once validated…
7.3🔒Canary 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…
7.4🔒Rolling 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…
7.5🔒Strategy Comparison
7.6🔒Feature 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.
7.7🔒Testing the Deployment Pipeline ItselfThe deployment pipeline is software. It can have bugs. Test it.
7.8🔒Career Translation- Designed and implemented blue-green deployment pipeline with automated pre-switch test validation, post-switch smoke tests, and instant…
7.9🔒Q&AInterview Depth CheckPrompt: Your team uses blue-green deployment. The green environment passes all tests, traffic switches, and then production smoke tests…