Summary: https://www.udemy.com/course/aws-certified-cloud-practitioner-new/learn/lecture/20260650
Global Applications
Ref: https://www.udemy.com/course/aws-certified-cloud-practitioner-new/learn/lecture/20056110 and https://www.udemy.com/course/aws-certified-cloud-practitioner-new/learn/lecture/29102360
- 🔧 Global application = app that is deployed in multiple geographic locations
- Benefits
- 👍 Decreased latency
- Users closer to infrastructure have lower latency
- If infrastructure deployed in multiple areas, more people will be closer to infra
- 👍 Resilience and Disaster Recovery (DR)
- If part of the infra goes down, other regions are still up → app can still operate
- Attack protection → distributed global infrastructure harder to attack
- Disadvantages
- 👎 Increased infrastructure costs
- More infrastructure means paying more
- 👎 More configurations, more management overhead
- Must use and configure global services, data replication, redundancy, and failovers
- 💡 In general, it makes sense to make an app global when the performance benefits are needed, or when it's starting to scale considerably in amount of users
| App deployment in AWS |
HA? |
Good global latency for reads? |
Good global latency for writes? |
| Single-region, single-AZ |
No |
No |
No |
| Single-region, multi-AZ |
Yes |
No |
No |
| Multi-region, Active-Passive |
Yes |
Yes |
No |
| Multi-region, Active-Active |
Yes |
Yes |
Yes |
Amazon Route 53
Ref: https://www.udemy.com/course/aws-certified-cloud-practitioner-new/learn/lecture/20056112
- 🔧 Global DNS service
- Can configure routing users to different infrastructure when they query a DNS endpoint
- Great for routing users to closest infra deployment (least latency)
- Great for DR strategy (route to a different resource if main resource is unhealthy)
- Some R53 routing policies:
- Simple Routing: no health checks, DNS endpoint always routes to same infra
- Failover Routing: health check on primary resource. If primary resource is unhealthy, route to secondary resource instead → simple DR strategy
- Weighted Routing: direct different amounts of traffic to different resources
- e.g. 70% of traffic to server A, 20% to server B, and 10% to server C → weights=70, 20, and 10
- Latency Routing: direct users to servers with lowest latency for them
Services Optimized for AWS Global Network
- Amazon CloudFront (CF): Global Content Delivery Network (CDN) in AWS
- Caches content to AWS edge locations
- Improves Read performance, decreases Read latency, improved UX
- S3 Transfer Acceleration: S3 uploads & downloads use AWS Global NW
- Client → AWS edge location → AWS global NW → S3
- Internet only used to connect client with edge location
- Accelerates speed of S3 reads & writes globally