Cloud Architecture Design Principles and Trade-offs Questions

Region vs AZ — short definitions:

• Region: a geographically isolated area (e.g., us-east-1, europe-west1, westeurope). Contains multiple AZs; used for data residency, disaster domain separation, and latency to users in that geography.
• Availability Zone (AZ): an independent failure domain within a region (separate data center or cluster with independent power/network). Examples: us-east-1a, europe-west1-b.

How each affects SRE decisions:

• Failure isolation: AZs protect against rack/DC-level faults. Design: run redundant instances across 2–3 AZs, use cross-AZ load balancing and distributed storage with synchronous or asynchronous replication. Regions protect against large-scale outages (power grid, region-wide network); multi-region is required for regional disasters.
• Latency: AZs inside a region have low inter-AZ latency (ms); prefer multi-AZ for typical HA. Cross-region latency is higher (tens to hundreds ms); use multi-region only when needed for geo-proximity or DR.
• Cost: AZ-redundancy costs less (data transfer inside region often cheaper); multi-region adds cross-region replication costs, duplicate infrastructure, and higher operational overhead.
• Data residency/compliance: Regions determine where data resides. For GDPR or local regulations pick region accordingly; multi-region may be constrained by legal rules.

Cloud nuances:

• AWS/GCP/Azure all offer multiple AZs per region; naming and exact isolation vary but design principles are the same. Watch for “soft” AZ mappings in some regions (e.g., smaller cloud regions with fewer AZs).

When to choose:

• Single-region, multiple-AZs: Use when you need high availability and low latency for a primary user base, and can accept region-level outages. Example: customer-facing web app serving a single continent with RPO minutes via multi-AZ DB replicas.
• Multi-region: Use when you need resilience to region failure, global low-latency presence, or legal residency across regions. Example: global SaaS with active-active reads in US and EU, writes routed to nearest region with cross-region async replication and conflict resolution.

Trade-offs summary:

• Multi-AZ: lower cost, simpler, fast failover, protects against most hardware/DC failures but not region-wide disasters.
• Multi-region: stronger disaster protection and geo-performance but higher cost, complexity (consistency, DNS failover, replication), and operational overhead.

Practical tip: start multi-AZ; add multi-region when SLOs require regional independence or legal/latency constraints demand it.