CDN & Edge Computing Guides

A CDN is the most-used networking feature on the public internet that most people never think about — every Netflix stream, every Instagram image, every npm download, every game patch comes through one. Modern CDNs also run application code at the edge, do TLS termination, mitigate DDoS, and act as the security gateway for entire websites. These guides explain how the major pieces work in plain English, with specific cache-header semantics, anycast routing details, and the operational trade-offs that determine whether a CDN deployment helps or hurts your application.

Where to start

If you are new to CDNs, start with how a CDN works — points of presence, anycast routing, and cache hit logic. Everything else builds on those fundamentals.

If you are debugging a specific cache problem, jump to cache-control headers — most CDN behavior is controlled by HTTP headers, and most bugs are misconfigured headers.

If you are building an application that runs code at the edge, see edge functions explained for the model differences between Cloudflare Workers, Lambda@Edge, and Vercel Edge.

CDN fundamentals

How content moves from origin to user via the CDN's distributed network.

Fundamentals

Cache Mechanics

Media at the Edge

Edge Computing

Operations & Security