> For the complete documentation index, see [llms.txt](https://huy312100.gitbook.io/software-development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://huy312100.gitbook.io/software-development/cloud-service/aws/certificate/clf-c02/cloud-technology-and-services/global-infrastructure/overview.md).

# Overview

### Why make a global application?

• A global application is an application deployed in multiple geographies

• On AWS: this could be Regions and/or Edge Locations

• Decreased Latency

* Latency is the time it takes for a network packet to reach a server
* It takes time for a packet from Asia to reach the US
* Deploy your applications closer to your users to decrease latency, a better experience

• Disaster Recovery (DR)

* If an AWS region goes down (earthquake, storms, power shutdown, politics)...
* You can fail over to another region and have your application still working
* A DR plan is important to increase the availability of your application

• Attack protection: distributed global infrastructure is harder to attack

### Global AWS Infrastructure

* Regions: For deploying applications and infrastructure
* Availability Zones: Made of multiple data centers
* Edge Locations (Points of Presence): for content delivery as close as possible to users
* More at: <https://infrastructure.aws/>

### Global Applications in AWS

• Global DNS: Route 53

* Great to route users to the closest deployment with the least latency
* Great for disaster recovery strategies

• Global Content Delivery Network (CDN): CloudFront

* Replicate part of your application to AWS Edge Locations – decrease latency
* Cache common requests – improved user experience and decreased latency

• S3 Transfer Acceleration

* Accelerate global uploads & downloads into Amazon S3

• AWS Global Accelerator:

* Improve global application availability and performance using the AWS global network