Thinking Global

Before you deploy a single line of C#, you must decide WHERE it lives. Choosing the right AWS Geography is the foundation of High Availability (HA) and Disaster Recovery (DR).

1. AWS Regions

A Region is a physical location in the world where AWS has multiple data centers. **Architect Hint:** Choose a region based on **Data Sovereignty laws** (e.g., GDPR requires data to stay in Europe) and **Latency** (choose the one closest to your users).

2. Availability Zones (AZs)

Each Region has multiple AZs. An AZ is one or more discrete data centers with redundant power and networking. **The Rule:** Never deploy your app to a single AZ. If a lightning strike or flood hits that data center, your app goes down. Always span your .NET fleet across at least 3 AZs for 99.99% uptime.

3. Edge Locations

These are NOT data centers where you run compute. They are small 'Points of Presence' (PoPs) used by **CloudFront (CDN)** to cache your frontend assets closer to users. This is what makes your website feel 'instant' globally.

3. Architect Insight

Q: "Does cost vary by region?"

Architect Answer: "YES. us-east-1 (N. Virginia) is usually the cheapest, while af-south-1 (Cape Town) or sa-east-1 (São Paulo) can be 20-50% more expensive. As an architect, you must balance cost against user latency. Use **AWS Pricing Calculator** before committing to a multi-region strategy."