# 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&#x20;
* Great for disaster recovery strategies

• Global Content Delivery Network (CDN): CloudFront

* Replicate part of your application to AWS Edge Locations – decrease latency&#x20;
* 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


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://huy312100.gitbook.io/software-development/cloud-service/aws/certificate/clf-c02/cloud-technology-and-services/global-infrastructure/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.