From One Zone to Zone-Resilient
Describe the practical changes required to move from a single-zone deployment to a zone-resilient deployment.
How did the support portal change so a single availability-zone outage is less likely to take it down? Before: duplicate resources, same zone After: resources span independent zones Placement changed: critical app capacity now exists in more than one zone, so one zone failing does not remove every serving instance. Data behavior changed: the database is configured for zone redundancy or standby replication, because stateless app copies alone do not protect state. Routing changed: health checks must stop sending users to failed-zone resources, otherwise redundant capacity exists but traffic still breaks. Evidence changed: the team runs a failover drill, because…
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in