AWS › AWS Global Infrastructure (Regions, AZs & Edge Locations)
How do you design a multi region architecture, and what are the key challenges involved compared to a multi Availability Zone design within a single region?
IntermediateAnswer
A multi region architecture involves running resources across entirely separate geographic AWS Regions, typically for disaster recovery, regulatory compliance across different countries, or to reduce latency for globally distributed users, but it introduces additional challenges compared to a single region multi Availability Zone design, including higher data transfer costs between regions, more complex data replication and consistency considerations, and the need to manage separate resource deployments since most AWS resources do not automatically span multiple regions.
aws dynamodb create-global-table --global-table-name Users --replication-group RegionName=us-east-1 RegionName=eu-west-1Real-world example A global social media platform deploys its application across both a United States region and a European region, using DynamoDB Global Tables to replicate user data between them, accepting the added architectural complexity in exchange for lower latency for users on both continents.