AWS Database Services: Global Database

In the AWS Certified Solutions Architect – Associate (SAA-C03) exam, “Global Database” refers to the specialized capabilities of Amazon Aurora and Amazon DynamoDB to span multiple AWS Regions. This is critical for building applications with a global footprint, requiring low-latency local reads and robust Disaster Recovery (DR).

The Global Library Analogy: Imagine a massive library in New York (Primary Region). Whenever a new book is added, it is instantly teleported to branch libraries in London, Tokyo, and Sydney (Secondary Regions). Local readers in those cities don’t have to fly to New York to read; they just go to their local branch. If the New York library burns down, the London branch can be promoted to the new main headquarters in minutes.

1. Amazon Aurora Global Database

Aurora Global Database is designed for globally distributed applications, allowing a single Aurora database to span multiple AWS Regions. It replicates data with no impact on database performance.

  • Architecture: One Primary AWS Region (Read/Write) and up to five Secondary Read-only Regions.
  • Replication: Uses dedicated infrastructure in the storage layer, keeping the compute resources free for application workloads.
  • Latency: Typically provides cross-region replication latency of less than 1 second.
  • Disaster Recovery: In the event of a regional outage, you can promote a secondary region to take full read/write workloads in less than a minute (RTO).

2. Amazon DynamoDB Global Tables

For NoSQL workloads, DynamoDB Global Tables provide a fully managed, multi-region, multi-active database. Unlike Aurora (which has one primary writer), DynamoDB Global Tables allow writes in any participating region.

  • Multi-Active: Every region is a “Primary.” You can write to US-East-1 and the data is replicated to EU-West-1 automatically.
  • Conflict Resolution: Uses “Last Writer Wins” based on timestamps to resolve concurrent updates to the same item.
  • Streams: Built upon DynamoDB Streams to track changes and propagate them across regions.

3. Comparison Table: Aurora vs. DynamoDB Global

Feature Aurora Global Database DynamoDB Global Tables
Database Type Relational (SQL) NoSQL (Key-Value/Document)
Write Pattern Single Region Writer (Primary) Multi-Region Writer (Multi-Active)
Replication Latency < 1 Second Sub-second (usually)
Failover Manual or Managed Promotion Automatic (Read/Write locally)
Use Case Complex joins, ACID compliance High-scale, simple lookups, mobile backends

Exam Tips and Gotchas

  • The “Standard” RDS Trap: Standard RDS (non-Aurora) supports “Cross-Region Read Replicas,” but it is NOT called a “Global Database.” Aurora is the only relational service with the “Global Database” branding and storage-level replication.
  • RPO/RTO: Aurora Global Database is the gold standard for low RPO (Recovery Point Objective) and RTO (Recovery Time Objective) in SQL scenarios.
  • Write Forwarding: Aurora Global Database supports “Write Forwarding,” allowing applications to send write requests to a secondary region, which are then forwarded to the primary.
  • Cost: Remember that you pay for the instances in every region and for the replicated data transfer between regions.

Decision Matrix / If–Then Guide

  • IF the requirement is a relational database with sub-minute DR failover… THEN use Aurora Global Database.
  • IF the requirement is a global NoSQL database where users in different continents must write to their local region… THEN use DynamoDB Global Tables.
  • IF the requirement is simply to offload read traffic from a standard RDS MySQL instance to another region… THEN use RDS Cross-Region Read Replicas.
  • IF you need to minimize latency for global users for a gaming leaderboard… THEN use DynamoDB Global Tables.

Topics covered :

Summary of key subtopics covered in this guide:

  • Aurora Global Database Architecture (Storage-level replication)
  • DynamoDB Global Tables (Multi-active replication)
  • Disaster Recovery (RPO/RTO) across regions
  • Cross-Region replication latency and performance
  • Relational vs. NoSQL global design patterns

Global Database Architecture Overview

Primary Region (e.g., us-east-1) Read/Write Cluster Physical Storage Replication (<1s Latency) Secondary Region (e.g., eu-west-1) Read-Only Cluster Promote to R/W during DR
Integrations

Service Ecosystem

  • IAM: Control access to clusters and table replication.
  • KMS: Data is encrypted at rest; same key is not used (Region-specific keys).
  • CloudWatch: Monitor AuroraGlobalDBReplicationLag.
Performance

Scaling & Latency

Secondary regions can have different instance sizes than the primary to save costs, but this may impact failover performance.

Pro Tip: Up to 16 Read Replicas per secondary region in Aurora.

Savings

Cost Optimization

  • Stop/Start is NOT supported for Aurora Global clusters.
  • Cross-region data transfer is a major cost driver.
  • Use DynamoDB On-Demand for unpredictable global traffic.

Production Use Case: Global E-Commerce

A retailer uses DynamoDB Global Tables for their user profile service. Customers in Tokyo and New York experience millisecond latency because they interact with their local regional endpoint. If a region goes down, the Route 53 health check redirects traffic to the nearest healthy region seamlessly.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top