How a CDN Works: Edge Servers, Caching and Latency Explained

Every second of load time costs you users. Amazon famously found that a 100ms delay costs them 1% in sales. Netflix streams to 190 countries without melting a single origin server. Both rely on the same invisible infrastructure: Content Delivery Networks. CDNs are not just a performance luxury — for any application with a global or even national audience, they're table stakes.

The problem CDNs solve is simple but brutal: physics. Data travels through fibre optic cables at roughly two-thirds the speed of light. A user in Tokyo requesting an image hosted in Frankfurt will wait 150–200ms just for the round trip — before a single byte of content is transferred. Multiply that by dozens of assets per page and you've already lost the user. A CDN collapses that distance by caching content at geographically distributed edge servers so the round trip becomes 5–20ms instead.

By the end of this article you'll understand exactly what happens from the moment a browser requests a CDN-backed URL to the moment the content arrives. You'll know the difference between origin pull and push CDNs, how cache invalidation actually works (and why it's harder than it sounds), and how to configure cache headers so your CDN behaves exactly as you intend — not randomly. You'll also walk away with the mental models that senior engineers use when debugging CDN behaviour in production.

What is CDN How It Works?

CDN How It Works is a core concept in CS Fundamentals. Rather than starting with a dry definition, let's see it in action and understand why it exists.

// TheCodeForge — CDN How It Works example
// Always use meaningful names, not x or n
public class ForgeExample {
    public static void main(String[] args) {
        String topic = "CDN How It Works";
        System.out.println("Learning: " + topic + " 🔥");
    }
}

Frequently Asked Questions