A parks recreation site suffers outages when in-place package updates fail mid-deploy on long-lived instances. Which deploy approach best reduces change-related downtime?
Select an answer to reveal the explanation.
Short Explanation
Blue/green is like swapping to a fresh stage set instead of rewiring lights mid-show. New ASG or ECS tasks go live only when healthy, and the old set stays until you cut over. Live SSH patching is how shows go dark.
Full Explanation
Immutable blue/green (or similar immutable) deployments via Auto Scaling groups or Amazon ECS launch a new healthy fleet and shift traffic, reducing the blast radius of failed changes. In-place SSH patching, single-server overwrites, and disabled health checks increase outage risk during municipal releases. Safer deploy patterns are part of designing for reliability, not only for feature velocity.