Skip to main content
PreparationZone Logo
PrepZone

Multi-Region Architecture

Active-active regions, data replication lag and routing users to the nearest healthy cluster.

Pass checkpoint below

Read these first

Why this matters

  • StreamHub serves 80M DAU across 120 countries — a single-region outage in us-east-1 would disconnect millions of viewers during peak events.
  • Latency to the nearest region matters: 200 ms round-trip to a distant data centre degrades live chat and video playback.
  • Data replication across regions introduces consistency trade-offs that must be designed per entity type.

Multi-region building blocks

  • GeoDNS / global load balancer — route users to nearest healthy region (Route 53, Cloudflare, GCP GLB).
  • Regional Kubernetes clusters — independent EKS/GKE clusters per region with identical service topology.
  • Cross-region replication — async database replication, S3 cross-region replication, Kafka MirrorMaker.
  • Conflict resolution — last-write-wins, version vectors, or region-scoped writes for contested data.
  • Failover automation — health checks trigger DNS failover when a region degrades.

Active-active topology

Multi-region active-active (AWS)

REGIONus-east-1ALB + EKS + RDS + S3
REGIONeu-west-1ALB + EKS + RDS + S3
REGIONap-southeast-1ALB + EKS + RDS + S3
NETWORKRoute 53latency routing
INTEGRATIONGlobal MSKcross-region sync
DATABASEDynamoDB Globalmulti-master
Route 53 latency routing → regional EKS stacks → async cross-region replication.
Java
# Route 53 latency-based routing
apiVersion: v1
kind: ConfigMap
metadata:
  name: dns-config
data:
  records: |
    streamhub.com:
      - region: us-east-1
        type: A
        routing_policy: latency
        health_check: /health
      - region: eu-west-1
        type: A
        routing_policy: latency
        health_check: /health
      - region: ap-south-1
        type: A
        routing_policy: latency
        health_check: /health

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 5 sections

  • Data replication strategies
  • Handling replication lag
  • Failover procedure
  • StreamHub regional deployment
  • Cost considerations

Test yourself

Answer these before moving on — recall is what makes it stick.