Recommended way to failover with DynamoDB Global tables?

Question

We are using Global tables in multiple regions with a single region for write operations. For automatic failover to a different region, can we use something on the application layer to change the writer region? Something like DNS to pick a healhy region, can result in writes to multiple regions while DNS propagates which is not safe as we use Transactions (not supported across multiple regions).

Answer

Please refer to the following Stack Overflow as it may be helpful. [1]

[1] amazon web services - DynamoDB Global Table - Stack Overflow  
https://stackoverflow.com/questions/59211708/dynamodb-global-table

Answer

When using Global Tables, DynamoDB is expected to handle this for you. The documentation does indicate that when you're using "strongly consistent reads" you may get stale data until the degradation is resolved.

However... whether a region is degraded or not, "Transactions are not supported across regions in global tables. Changes will eventually be replicated to other regions once they have been committed in the source region." See Using transactional APIs with global tables.

However... whether a region is degraded or not, "Transactions are not supported across regions in global tables.  Changes will eventually be replicated to other regions once they have been committed in the source region."  See [Using transactional APIs with global tables](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/transaction-apis.html).

Recommended way to failover with DynamoDB Global tables?

相關內容