- Learn AWS
- Architecture
- Global multi-region
Architecture pattern
AWS Global multi-region architecture
when users on several continents need the app to feel local
A full stack in each region and DNS sending people to the nearest healthy one. The edge absorbs the static and cacheable traffic; the regional stack handles what has to be computed near the user.
What it runs through
In the order a request or a record moves through it. Each one links to the page that explains it.
- Route 53Amazon Route 53
- CloudFrontAmazon CloudFront
- ALBApplication Load Balancer
- ECS on FargateAmazon ECS on AWS Fargate
- DynamoDBAmazon DynamoDB
Signals in a brief that point here
Phrases that, when you meet them in a scenario, mean this shape rather than another. They are the tell, and they are what an exam question is built around.
- “India, Europe, North America”
- “low latency globally”
- “regional failover”
- “data residency”
What it costs you
Replicating writes across regions is the hard part, and multi-region consistency is where these designs usually break.
Every shape has one. A design decision with no stated downside is usually a decision nobody has finished making.
Learn the services in it
- AWS Route 53AWS's DNS service. It registers domains, answers queries for them with a choice of routing policies, and sends traffic away from endpoints that fail their health checks.
- AWS CloudFrontA content delivery network: copies of your files are cached at edge locations near viewers, and requests that miss go back to your origin over the AWS network.
- AWS ELBSpreads incoming traffic across healthy targets in several Availability Zones, with four kinds of load balancer: Application, Network, Gateway and Classic.
- AWS DynamoDBA serverless key-value and document database with single-digit millisecond responses at any scale, and DAX, its in-memory cache, for microseconds.
Shapes it is easily confused with
These run through some of the same services, which is exactly why a brief that fits one can look like it fits another.
Now build it from a brief
Reading a shape and producing one from a scenario that never names a service are different skills, and the exam asks for the second. The scenarios give you the brief; you draw the architecture and it is scored against what the brief requires.