2 Answers
- Newest
- Most votes
- Most comments
0
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.
answered 2 years ago
0
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
answered 2 years ago
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
My Question is more around how to fix a particular region as primary. I can still do transactions when I fix one region and use other regions as passive backups. The question is what's the safest and quickest way to switch to another region for writing when the primary region is down.