A CDN, or content delivery network, is a system of geographically distributed servers that work together to deliver web content faster. When you load a webpage, your browser doesn't always have to reach the original server halfway around the world. A CDN intercepts that request and serves the content from a nearby node instead, often shaving hundreds of milliseconds off the load time. That gap sounds small, but it shapes whether people stay on a page or leave.
What a CDN actually does
At its core, a CDN caches static content: images, videos, CSS stylesheets, JavaScript files, and HTML pages. It stores copies of those files on servers called points of presence, or PoPs, positioned in data centres across multiple cities and countries. When a user in Brisbane requests a file that sits on an origin server in Frankfurt, the CDN routes that request to the nearest PoP, perhaps in Sydney, and serves the cached copy from there.
The original server only needs to be contacted when the CDN doesn't already have a fresh copy of the file. That event is called a cache miss. Once the CDN fetches and stores the file, every subsequent request for it becomes a cache hit, served locally without touching the origin. For a site with millions of visitors, this dramatically reduces the load on the origin server.
CDNs don't only serve static content. Modern networks also accelerate dynamic requests, those that require real-time database queries, by optimising routing paths between the user and the origin. This is sometimes called dynamic site acceleration, and it works by finding the fastest network path rather than caching the result.
How CDNs route your request
When you type a URL into your browser, the first step is a DNS lookup: your device asks a DNS server to translate the domain name into an IP address. If the domain uses a CDN, the DNS response doesn't return the origin server's address. It returns the address of the nearest CDN edge server. This redirection is invisible to you.
CDN providers use several techniques to decide which edge server to send you to. Anycast routing is one common approach: multiple servers share the same IP address, and the network automatically directs your request to the closest one. Other providers use DNS-based load balancing, returning a different IP address depending on where the DNS query originates. The end result is the same: your request lands on a server close to you, and the content arrives faster.
Understanding this routing process is easier if you already have a handle on how DNS translates domain names into IP addresses, since CDNs build directly on top of that infrastructure.
Security benefits that come with a CDN
CDNs do more than speed things up. Because edge servers sit between users and the origin, they act as a buffer against certain attacks. A distributed denial-of-service attack floods a server with fake traffic until it collapses. A CDN can absorb that traffic across its distributed network, spreading the load so no single server is overwhelmed. Large CDN providers like Cloudflare maintain enormous network capacity precisely for this reason.
CDNs also enforce HTTPS at the edge, terminate TLS connections close to the user, and can apply web application firewall rules to filter malicious requests before they reach the origin. For smaller sites that can't afford dedicated security infrastructure, a CDN provides a meaningful baseline of protection at relatively low cost.
This overlaps with broader network security concepts. If you want to understand how traffic filtering works at a deeper level, the article on what a firewall does and how it protects your network covers the underlying principles well.
Who uses CDNs and why it matters for ordinary Australians
Almost every major website you visit uses a CDN. Streaming services, news sites, e-commerce platforms, social media networks: all of them rely on CDN infrastructure to serve content at scale. When Netflix loads a video in under two seconds on a slow connection, that's a CDN doing its job. When a major retail site survives a Black Friday spike in traffic without crashing, the same infrastructure is at work.
For Australians, CDNs are particularly significant. Australia's geographic isolation means that origin servers in the United States or Europe are genuinely far away, and network latency reflects that. A well-configured CDN with PoPs in Sydney, Melbourne, and Perth can cut load times from two or three seconds down to under half a second for local users. That's not a minor convenience. It's the difference between a site feeling responsive and one that feels broken.
Small businesses and independent developers can access CDN services cheaply through providers like Cloudflare, Amazon CloudFront, and Fastly. Many offer generous free tiers. A WordPress blog with a CDN in front of it can handle traffic spikes that would otherwise take it offline.
Cache invalidation: the hard part
CDNs work beautifully when content doesn't change. The hard problem is telling the CDN that a cached file is no longer valid. This is called cache invalidation, and it's notoriously tricky to get right.
If a developer pushes an update to a JavaScript file but the CDN still serves the old version, users see a broken site. Solutions include versioning file names (so a new file gets a new URL that the cache treats as fresh), setting short cache expiry times for content that changes often, and issuing manual purge commands through the CDN's control panel. Each approach has trade-offs between freshness and performance.
Getting invalidation wrong is one of the most common reasons a site update seems to "not work" for some users but not others. The users seeing the old version are hitting a PoP that hasn't yet received the purge command.
The difference between a CDN and a web host
A web host stores your website's files and runs the software that generates your pages. A CDN doesn't host your site: it copies and distributes the output of your host to locations closer to your users. The origin server still exists. The CDN just means most visitors never have to reach it directly.
Some hosting providers bundle basic CDN functionality into their plans, which can create confusion. A host that says it includes a "global CDN" is usually offering edge caching in a handful of cities. Dedicated CDN providers operate hundreds of PoPs and offer more sophisticated routing, analytics, and security tools. For high-traffic sites, the distinction matters. For a personal blog, the bundled option is almost always enough.
CDNs are one layer in a broader stack. The network still depends on the same routers, protocols, and physical cables that carry all internet traffic. If you want to understand how devices connect at the local level before traffic ever reaches a CDN, the article on what a LAN is and how it works covers that foundation clearly.