Multi-Region Architecture
Surviving a region, and the data consistency price of doing so.
5 to work through
-
advanced
A collaborative design tool has users in one document spread across continents, needing sub-100 ms feedback on every edit. Should the document's authoritative state be multi-region writable, single-region, or something else?
2 min answer -
advanced
A global retailer wants a single product catalogue with sub-100ms writes from anywhere and strong consistency. Assess.
2 min answer -
advanced
A globally distributed application routes users to nearby regions but holds state that cannot safely be duplicated. Which components should be regional, which globally replicated, and which operations should stop during a regional outage?
2 min answer -
advanced
A multi-region active-active deployment allows writes in every region. Classify entities by the conflict strategy each needs, and describe how cross-region failover should be tested.
2 min answer -
advanced
Leadership asks for multi-region "for resilience". What do you establish before designing anything?
2 min answer
6 terms in this topic
Active-Active vs Active-Passive
Whether all regions serve traffic simultaneously, or one serves while another waits to take over — a choice about which failure mode you would rather have.
patternEntity Homing
Assigning each entity - customer, account, tenant - a single home region that owns its writes, so a regional outage affects a subset of entities rath…
toolGlobal Traffic Management
The layer that decides which region a given user reaches, using DNS, anycast or an edge network, and that performs regional failover.
patternMulti-Region Active-Active
Serving live traffic from two or more regions simultaneously, which removes failover time and introduces distributed data problems permanently.
case-studyNetflix: Regional Evacuation
Netflix rehearses shifting all traffic out of an entire AWS region, which is what makes the capability real rather than documented.
practiceRegional Evacuation
The deliberate, rehearsed act of shifting all traffic out of a region — treated as a routine operation rather than an emergency procedure.
Neighbouring topics
Cloud Architecture
General material on designing for cloud platforms.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Cloud Storage
Object, block and file storage, and the access patterns each suits.
Cloud Databases
Managed relational, key-value, document and analytical services.
Containers
Images, registries, immutability and the deployment model they enable.
Kubernetes
The reconciliation loop, and whether the workload needs what it provides.
Serverless
Scale to zero, per-request billing, cold starts and connection limits.
Autoscaling
Signals, delays and bounds — and the maximum that caps a runaway bill.
Load Balancing
Distributing traffic, health checking, and removing failures from rotation.
Availability Zones
The unit of correlated physical failure, and what zones do not protect against.
Disaster Recovery
Backup-restore, pilot light, warm standby and active-active postures.
Backup Strategies
Scope, immutability, separation, and the restore drill that makes it real.
Infrastructure as Code
Declarative infrastructure, drift, state files and rebuild-from-empty.
Landing Zones
A governed foundation of accounts, network, identity and guardrails.
Managed Services
Which operational responsibilities actually transfer, and which do not.
Cloud Migration
Per-application disposition, sequencing and the capability change underneath.
Multi-Cloud
Best-of-breed, portfolio and portable — three very different costs.
Edge Computing
Moving compute towards the user, and what cannot follow it.
Cloud Governance
Preventive policy, tagging, quotas and cost and security guardrails.