Streams as the Engine Behind Global Tables
~10 min read
How the same Streams mechanism that powers event-driven Lambda triggers is also what makes Global Tables' replication work.
Streams as the Engine Behind Global Tables is a Pro topic
Sign in, then upgrade to Pro or Power to unlock this topic and the full AWS curriculum.
Key points
- •Global Tables use DynamoDB Streams internally to propagate writes between participating Regions
- •Enabling Global Tables auto-enables Streams on the table if not already active
- •Streams supports multiple independent consumers — your own Lambda trigger and Global Tables' replication can coexist
- •An outage longer than the 24-hour Streams retention window can force a full resync rather than incremental catch-up