What is a CDN and how does it improve performance?

Question

Accepted Answer

A **CDN (Content Delivery Network)** is a network of geographically-distributed servers that **cache and serve content from locations near users** — reducing latency and offloading origin servers. It's a key component for fast, global content delivery.

## What a CDN does

```text
A CDN caches content at EDGE locations (servers) around the world:
  → users get content from the NEAREST edge server (not the distant origin)
  → reduces LATENCY (shorter distance = faster) for global users
  → offloads the ORIGIN server (edges serve cached content → less origin load)
  User → nearest CDN EDGE (cached? serve it) → on miss, fetch from origin, then cache
```

## What CDNs serve

```text
✓ STATIC content → images, CSS, JS, videos, fonts, downloads (the classic use)
✓ Increasingly dynamic content, API responses (edge computing/caching)
✓ Large media (video streaming); software distribution
```

## Benefits

```text
✓ PERFORMANCE → much faster loads for users worldwide (content served nearby)
✓ SCALABILITY → CDN handles huge traffic; offloads your origin (it serves far less)
✓ AVAILABILITY → distributed; absorbs traffic spikes; some DDoS protection
✓ COST → reduces bandwidth/load on origin servers
→ essential for global-scale, performant web applications and media delivery
```

## Why it matters

Understanding CDNs is foundational because they're a **key component for fast, global content delivery and scalability**, so it's important system-design knowledge.

A CDN — a network of geographically-distributed edge servers that cache and serve content near users — addresses the fundamental problem that serving content from a distant origin server is slow for global users.

By **serving content from the nearest edge location**, a CDN reduces **latency** (shorter distance means faster delivery, improving performance for users worldwide) and **offloads the origin** (edges serving cached content, reducing origin load and improving scalability).

Understanding **what CDNs serve** — classically static content (images, CSS, JS, videos, fonts) and increasingly dynamic content and API responses (edge computing) — clarifies their use.

Understanding the **benefits** — performance (much faster loads globally), scalability (handling huge traffic and offloading the origin), availability (distributed, absorbing spikes, some DDoS protection), and cost reduction (less origin bandwidth) — explains why CDNs are essential for global-scale, performant web applications and media delivery.

CDNs are a standard component in system design for any application serving users globally or delivering significant static content/media.

Since fast, global content delivery and offloading origin servers are important for performant, scalable systems, and since CDNs (caching content at edge locations near users) are the key mechanism for this, and since understanding what they do and their benefits is important for system design, understanding CDNs is essential, foundational system-design knowledge — a key component for global performance and scalability, standard in designing systems that serve users worldwide or deliver static content and media, and an important building block for fast, scalable web applications.