Content Delivery Networks

Every time you stream a video, load a news article, or download a software update, the bits travel from a server to your device. The speed of light sets a hard floor: a signal crossing the Atlantic takes at least 70 milliseconds one-way, no matter how fast the link. Add routers, congestion, and protocol handshakes and the round-trip can easily reach half a second.

A Content Delivery Network (CDN) cuts that delay by refusing to let your request cross the globe in the first place. Instead of one central server, a CDN operates hundreds of Points of Presence (PoPs) scattered across continents — data centers positioned as close as possible to where real users live.

The two mechanisms that make this work are elegantly simple: anycast routing steers each packet to the geographically nearest PoP automatically, and edge caching stores a copy of popular content right there, so it can be served without ever reaching the origin server. Together they turn a global audience into a crowd of local visitors.

The map below shows a simplified globe with several CDN Points of Presence (PoPs). Click anywhere to drop a user — the demo will instantly highlight which PoP is closest and simulate the latency savings compared to fetching from a single origin server.

<!-- {{c_html_comment}} -->
<div class="layout">
  <div class="map-wrap">
    <svg id="map" viewBox="0 0 500 280" xmlns="http://www.w3.org/2000/svg" aria-label="{{map_aria}}">
      <!-- {{c_svg_bg}} -->
      <rect width="500" height="280" fill="#e8f0f7" rx="8"/>
      <!-- {{c_continents}} -->
      <!-- North America -->
      <path d="M60,40 L140,35 L155,80 L130,120 L80,130 L55,100 Z" fill="#c9d8e8" stroke="#a0b8cc" stroke-width="1"/>
      <!-- South America -->
      <path d="M105,145 L145,140 L155,190 L130,240 L95,235 L85,185 Z" fill="#c9d8e8" stroke="#a0b8cc" stroke-width="1"/>
      <!-- Europe -->
      <path d="M210,30 L255,28 L260,70 L235,80 L210,65 Z" fill="#c9d8e8" stroke="#a0b8cc" stroke-width="1"/>
      <!-- Africa -->
      <path d="M210,90 L255,85 L260,155 L235,200 L205,195 L195,145 Z" fill="#c9d8e8" stroke="#a0b8cc" stroke-width="1"/>
      <!-- Asia -->
      <path d="M270,25 L410,20 L415,110 L370,130 L300,125 L265,90 Z" fill="#c9d8e8" stroke="#a0b8cc" stroke-width="1"/>
      <!-- Oceania -->
      <path d="M355,160 L410,155 L415,205 L375,215 L345,200 Z" fill="#c9d8e8" stroke="#a0b8cc" stroke-width="1"/>
      <!-- {{c_pop_group}} -->
      <g id="pops"></g>
      <!-- {{c_user_group}} -->
      <g id="user-group"></g>
      <!-- {{c_line_group}} -->
      <g id="lines"></g>
    </svg>
    <p class="hint">{{hint_click}}</p>
  </div>
  <div class="panel">
    <h3 class="panel-title">{{panel_title}}</h3>
    <div id="result" class="result-idle">{{result_idle}}</div>
    <div id="stats" class="stats hidden">
      <div class="stat-row"><span class="stat-label">{{label_nearest}}</span><span id="nearest-name" class="stat-val"></span></div>
      <div class="stat-row"><span class="stat-label">{{label_edge_lat}}</span><span id="edge-lat" class="stat-val"></span></div>
      <div class="stat-row"><span class="stat-label">{{label_origin_lat}}</span><span id="origin-lat" class="stat-val"></span></div>
      <div class="stat-row"><span class="stat-label">{{label_saving}}</span><span id="saving" class="stat-val green"></span></div>
      <div class="stat-row"><span class="stat-label">{{label_cache}}</span><span id="cache-hit" class="stat-val"></span></div>
    </div>
    <button id="btn-reset" type="button" class="ghost">{{btn_reset}}</button>
  </div>
</div>

/* {{c_css_reset}} */
* { box-sizing: border-box; margin: 0; padding: 0; }
body { font-family: system-ui, sans-serif; color: #222; }
.layout { display: flex; gap: 12px; align-items: flex-start; flex-wrap: wrap; }
.map-wrap { flex: 1 1 300px; }
#map { width: 100%; height: auto; cursor: crosshair; border-radius: 8px;
       border: 1px solid #c5d5e5; display: block; }
/* {{c_hint_style}} */
.hint { font-size: .8rem; color: #555; margin-top: 6px; text-align: center; }
/* {{c_panel_style}} */
.panel { flex: 0 0 180px; background: #f0f5fa; border: 1px solid #c5d5e5;
         border-radius: 8px; padding: 12px; display: flex; flex-direction: column; gap: 8px; }
.panel-title { font-size: .85rem; font-weight: 700; color: #1d3557; }
.result-idle { font-size: .8rem; color: #888; }
.stats { display: flex; flex-direction: column; gap: 6px; }
.hidden { display: none; }
.stat-row { display: flex; flex-direction: column; }
.stat-label { font-size: .7rem; color: #666; text-transform: uppercase; letter-spacing: .03em; }
.stat-val { font-size: .9rem; font-weight: 700; color: #1d3557; }
.stat-val.green { color: #0a7d33; }
/* {{c_btn_style}} */
button.ghost { font: 600 13px system-ui; padding: .35rem .7rem; border: 1px solid #1d3557;
               background: #fff; color: #1d3557; border-radius: 6px; cursor: pointer; margin-top: 4px; }
/* {{c_pop_circle}} */
.pop-circle { fill: #1d3557; opacity: .85; transition: r .15s; cursor: default; }
.pop-circle.active { fill: #e63946; opacity: 1; }
.pop-label { font-size: 9px; fill: #1d3557; font-weight: 600; text-anchor: middle; pointer-events: none; }
/* {{c_user_dot}} */
.user-dot { fill: #f4a261; stroke: #e76f51; stroke-width: 1.5; }
/* {{c_conn_line}} */
.conn-line { stroke: #e63946; stroke-width: 1.5; stroke-dasharray: 4 3; opacity: .7; }
.origin-line { stroke: #888; stroke-width: 1; stroke-dasharray: 3 4; opacity: .45; }

// Code not found

Notice how the closest PoP wins every time, regardless of which continent you click. That is anycast in action: the network announces the same IP address from every PoP, and BGP routing automatically selects the shortest path. The cache hit ratio shown in the panel matters just as much — a cold cache forces a round-trip to the origin, wiping out the proximity advantage.

"Put a server near every user" sounds easy. The engineering underneath is not.

• PoP placement is a facility location problem. You want to cover the maximum user population while minimizing the number of sites — a classic NP-hard optimization. CDN operators solve it with heuristics tuned to traffic maps and peering costs.
• Anycast relies on BGP, not geometry. Border Gateway Protocol finds the shortest AS-hop path, not the shortest physical distance. A PoP 500 km away but well-peered can win over one 200 km away behind a slow link. Operators tune BGP communities and local-preference to nudge traffic where they want it.
• Cache eviction is a bet on the future. Every PoP has finite storage. Policies like LRU, LFU, and adaptive variants (ARC, LIRS) try to keep the objects most likely to be requested next. A poor eviction strategy collapses cache-hit ratios and floods the origin.
• Consistent hashing distributes load without reshuffling. When a PoP is added or removed, only $\frac{1}{n}$ of cached keys need to move, not the whole keyspace — the same insight behind distributed hash tables and load balancing.
• Cache coherence under updates is subtle. When the origin changes a file, stale copies in hundreds of PoPs must be invalidated or refreshed without creating thundering-herd requests to the origin all at once.

Each of these sub-problems has decades of research behind it. A CDN is not a single algorithm — it is a stack of interacting optimization problems, each with its own tradeoff between consistency, latency, and cost.

CDNs have quietly become the load-bearing infrastructure of the internet:

• Video streaming: platforms like YouTube and Netflix deliver petabytes per day because each regional PoP caches the most popular titles. Without edge caches, every play button would hammer a handful of origin data centers.
• Static web assets: CSS, JavaScript, and images for major sites are served from CDN edges. A well-configured CDN can cut page-load times by 50–70 % for users far from the origin.
• DDoS mitigation: because anycast spreads traffic across hundreds of nodes, a volumetric attack is absorbed by the whole network rather than hitting one target. This is how CDN providers absorb terabit-scale attacks.
• Edge computing: modern CDN platforms (Cloudflare Workers, Fastly Compute) let developers run code at the PoP, enabling personalization, A/B testing, and authentication without a round-trip to the origin.
• Software and game distribution: operating-system updates and game patches are multi-gigabyte files downloaded by millions simultaneously. CDN caching prevents the origin from being crushed on launch day.

The same ideas — proximity, caching, and distributed routing — also appear in peer-to-peer networks and in how browsers cache DNS responses locally, compounding the latency savings at every layer.

Content Delivery Networks are a beautiful collision of geography and computer science. The speed of light is an unbreakable law of physics — but anycast routing and edge caching sidestep it by ensuring that most requests never have to travel far at all.

Behind the simple idea of "serve from nearby" sit hard problems: optimal facility placement, BGP path engineering, cache eviction theory, and consistent hashing. Each is a rich area of algorithmic research in its own right. The CDN is proof that distributed systems, when designed carefully, can make a planet-sized network feel as responsive as a local loop.