Internet & Networking

CDN (Content Delivery Network)

A CDN (Content Delivery Network) is a network of servers spread around the world that stores copies of website content — like images, videos, and web pages — so that it can be delivered to users from a location close to them.

Instead of every request travelling to one distant server, a CDN serves content from the nearest available point, making websites load faster for everyone regardless of where they are.

CDN (Content Delivery Network), explained at three levels

At home

A CDN stores copies of a website's content on servers in many locations around the world. When you visit a website that uses a CDN, the content is loaded from a server near you rather than from one far away. This is why a website hosted in the US can still load quickly for someone in Australia — the CDN has a copy nearby. You benefit from CDNs every day without realising it, as most major websites and streaming services use them.

At work

For businesses, a CDN improves website performance for users globally, reduces the load on the origin server, and provides resilience against traffic spikes and some types of cyberattacks. If your company's website or web application serves users across different regions, a CDN can dramatically improve their experience. CDN services (Cloudflare, AWS CloudFront, Akamai, Fastly) are typically straightforward to implement and offer significant performance returns relative to their cost.

Real-world examples

At home

When Mei watches a cooking video on a streaming platform, the video does not stream all the way from a server in California. Instead, a CDN has copies of the video stored on a server in her city. The video plays quickly and smoothly because the data only needs to travel a short distance to reach her, rather than crossing an ocean.

At work

When Carlos's e-commerce company runs a flash sale that causes a massive spike in website traffic, the CDN absorbs the surge by serving cached product images, stylesheets, and JavaScript files from edge servers worldwide. The origin server only handles the dynamic parts (cart, checkout), preventing it from being overwhelmed. Without the CDN, the site would likely slow to a crawl or crash under the load.

Common confusions

  • It's often assumed that CDNs replace web servers. A CDN works alongside your server, caching copies of content while the origin server remains the authoritative source.
  • You might think only big companies need a CDN. CDNs are affordable, easy to implement, and benefit websites of any size with faster loading, DDoS protection, and improved reliability.
  • It's tempting to think CDNs only help with static files. Modern CDNs also accelerate dynamic content and offer edge computing, security, and optimisation features.

For analysts

If your project involves a website or web application that serves users in multiple regions, include a CDN in the architecture from the start rather than treating it as a later optimisation. Specify the caching strategy in your requirements — which content should be cached and for how long — and plan for cache invalidation when content is updated. A well-configured CDN is one of the highest-impact, lowest-effort performance improvements available.

History & origin

The concept of content delivery networks was pioneered in the late 1990s, with Akamai Technologies founding one of the first CDN services in 1998. Early CDNs primarily cached static content like images to reduce load on origin servers. As streaming video, cloud applications, and global audiences grew throughout the 2000s and 2010s, CDNs became essential infrastructure that now delivers a majority of all internet traffic worldwide.