6.2. DNS, Content Delivery, and Global Acceleration

💡 First Principle: Geography is physics. Without a CDN, every user in Tokyo hitting an origin in us-east-1 experiences 150ms of unavoidable latency — and under high load, the origin becomes a bottleneck that affects all global users. Think of it like the difference between calling someone next door versus someone on the other side of the world: the round-trip time is physically constrained by distance. CloudFront edge caches are like local post offices — rather than every letter traveling to headquarters, common items are stocked nearby. Unlike a single-origin architecture, CDN distribution means most requests never reach your origin at all. Light travels at a finite speed — roughly 200,000 km/s through fiber. A user in Tokyo making a request to a server in us-east-1 has a baseline round-trip latency of ~170ms before any application processing happens. Content delivery and global acceleration services move data closer to users, reducing the physical distance that network packets must travel.

DNS also plays a critical traffic-routing role. Route 53 routing policies aren't just name resolution — they're traffic management decisions that happen before a packet ever reaches your infrastructure. A well-designed DNS strategy can eliminate regional failures from the user's perspective by redirecting traffic to healthy endpoints automatically.