Blue-green: maintain two production environments; deploy and verify the new version on the idle one, then cut traffic over, enabling near-zero-downtime releases.
2 / 5
What is the main benefit of blue-green for rollback?
Fast rollback: because the previous (blue) environment is still running, reverting is just flipping the router back, far quicker than redeploying old code.
3 / 5
What is a key cost of blue-green deployments?
Cost: maintaining duplicate capacity is more expensive than in-place updates, though it can be temporary if the old environment is torn down after the cutover.
4 / 5
What challenge do database schema changes pose for blue-green?
Schema compatibility: since blue and green often share a database during the transition, migrations should be additive/backward-compatible (expand-contract) to avoid breaking either version.
5 / 5
How does blue-green differ from a canary release?
vs canary: blue-green is an all-at-once cutover between two environments, whereas canary incrementally routes a fraction of traffic to the new version to limit risk.