Building an architecture for a single data center is straightforward. Building an architecture that operates reliably across continents—North America, Europe, and Asia-Pacific—forces engineers to confront the ultimate physical constraint: the speed of light in optical fiber ().

A packet traveling from London to Sydney takes over 150 milliseconds round-trip. If your architecture requires synchronous cross-region database locks, every single user interaction will stall. Conversely, if each region accepts writes independently, network partitions and concurrent writes generate conflicting state.

This module deconstructs global systems engineering:

  • Global Ingress: How BGP Anycast and GeoDNS route millions of users to the nearest edge Point of Presence (PoP) in sub-10ms.
  • Active-Passive vs. Active-Active Topologies: Why multi-region failovers fail if standby regions are not running live production traffic.
  • Cross-Region Conflict Resolution: Managing concurrent updates across regions using Conflict-Free Replicated Data Types (CRDTs), Last-Write-Wins (LWW) with synchronized clocks, and deterministic tie-breaking.
  • Disaster Recovery Topologies: Designing architectures to meet strict RPO (data loss window) and RTO (recovery time window) SLAs during full data center outages.

What you will learn

  • Compare BGP Anycast and Latency-based GeoDNS routing mechanisms for steering global users to optimal regional data centers
  • Architect Active-Active multi-region deployments: evaluate single-leader global routing vs. multi-leader writes with CRDT conflict resolution
  • Calculate the speed-of-light cross-continental latency floor and evaluate its impact on synchronous consensus protocols (Paxos/Spanner TrueTime)
  • Design automated cross-region disaster recovery runbooks balancing Recovery Point Objective (RPO) against Recovery Time Objective (RTO)
STAGE TOPICS

Topics in this chapter