Chapter 8. AWS Global Infrastructure
A global application is one that’s deployed across multiple geographic locations. In AWS, this typically means leveraging multiple AWS Regions, Availability Zones, and Edge Locations. The main benefit of this setup is that users will experience less delay when interacting with your application. Because of the sheer size of the planet, a user in India accessing a server in the United States will experience noticeable lag. But if your application is deployed closer to where your users are—say, in both the US and Asia—then everyone benefits from faster, more responsive performance.
Another major reason to go global is disaster recovery. You may not want to rely solely on a single AWS Region. While AWS is highly reliable, disasters like earthquakes, power outages, or political instability can impact a Region. Deploying your application across multiple Regions enhances resilience by enabling failover if one Region goes down. To make this seamless, however, you need to configure replication (such as S3 Cross-Region Replication), implement solid backup strategies, and use services like Amazon Route 53 for DNS failover. This layered approach ensures redundancy, maximizes uptime, and keeps your applications highly available even during Regional disruptions.
Finally, distributing your application globally can also strengthen defenses against cyberattacks. Threats like DDoS attacks are unfortunately common, but spreading infrastructure across multiple ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access