Article: You Should Always Use DynamoDB Global Tables Now
category: Amazon DynamoDB
Thoughts on the new Global Tables Resource for CloudFormation announced mid May 2021.
Interesting quotes:
Interesting quotes:
* This leans even harder into the best practice of defining your DynamoDB table in its own stack. Expand to new regions at your data layer first before you expand your application!
* "AWS::DynamoDB::Table vs AWS::DynamoDB::GlobalTable" ==> Functionally, the two types of resources operate in exactly the same way when you deploy a CloudFormation stack. If you’re building an app that will ever only be in a single region – ok, I grant you there’s maybe not a reason to always default to AWS::DynamoDB::GlobalTable. But if you’re building an app where you plan to expand to multiple regions, or want to leave the door open to do so, you should just use it and ease the burden of multi-region expansion later on. The point is the option is there even if you never turn it on! And, of course, if you are building a multi-region app backed by DynamoDB, this is a no brainer.
Link (article):
https://acloudguru.com/blog/engineering/you-should-always-use-dynamodb-global-tables-now