Global tables, replication and streams, oh my!

Question

We are planning to use DynamoDB global tables to enable automatic replication to our failover region. Our primary region is us-east-1 where several of our processes need to run because that is the only instance of the CloudFront control plane. In the event of a us-east-1 outage, we will redirect to our failover region, which will be making changes to the DynamoDB instance there. When us-east-1 comes back online, I'm expecting replication to kick in and make the necessary changes there, right?

Now here's the tricky part. We initiate background tasks (which must run in us-east-1, or at least when us-east-1 is alive) based on changes to the data via DynamoDB streams. When replication happens in us-east-1, will those streams be triggered just as if a service had updated the database?

Now here's the tricky part.  We initiate background tasks (which must run in us-east-1, or at least when us-east-1 is alive) based on changes to the data via DynamoDB streams.  When replication happens in us-east-1, will those streams be triggered just as if a service had updated the database?

Answer

If there was issue in us-east-1 and replication was paused, when the region comes back online, DynamoDB will replicate what every changes happened in your secondary region to us-east-1 table and it will trigger the streams just as if you wrote to that region at the point of replication.

Global tables, replication and streams, oh my!

Relevant content