Skip to content

Content Delivery Networks

Abstract

The web has a physics problem: one server, one building, one cable, and a planet of users. In 1995 Tim Berners-Lee, newly at MIT, posed the congestion problem to the algorithms group down the hall. The answer (consistent hashing, from Tom Leighton’s group and his student Danny Lewin) became Akamai (1998), the company that invented the content delivery network: thousands of cache servers pushed to the internet’s edge, so that content is served from around the corner instead of across the ocean. CDNs carried the Starr Report era’s traffic spikes, the Phantom Menace trailer, every World Cup, and (the morning its own co-founder was murdered aboard Flight 11) the news of September 11. Today a handful of CDNs (Akamai, Cloudflare, CloudFront, Fastly) sit in front of most of the web, which means the network built to eliminate single points of failure has become the closest thing the web has to one: when Cloudflare stumbles, “half the internet” returns error 500.

Berners-Lee’s Challenge

At MIT’s Laboratory for Computer Science, Tim Berners-Lee watched his invention start to choke on its own success (“flash crowds” and “hot spots,” whole sites unreachable the moment they mattered most) and in 1995 challenged MIT’s theorists to invent a better way. Tom Leighton, an applied-mathematics professor whose office was down the hall, took it as an algorithms problem. With graduate student Daniel Lewin and colleagues, the group produced consistent hashing (Karger, Lehman, Leighton, Levine, Lewin, Panigrahy, STOC 1997): a way to spread objects across a changing pool of cache servers so that when machines join or die, almost nothing needs to move. It is the rare STOC paper that became both billion-dollar infrastructure and a standard job-interview question, the same primitive later powering Amazon’s Dynamo and most distributed databases.

Akamai: The Edge Is Born

Leighton and Lewin entered the MIT $50K entrepreneurship competition and incorporated Akamai (Hawaiian for clever) on August 20, 1998. Commercial launch came in April 1999, and the proof events arrived on cue: ESPN’s March Madness traffic and the Star Wars: Episode I trailer (the kind of demand spikes that melted origin servers) sailed through Akamai’s distributed caches. The model: deploy servers inside ISP networks everywhere, map each user to a nearby healthy server via DNS in real time, and charge content owners for the delivery. In October 1999 Akamai went public into the bubble’s final ascent; the stock rose over 400% on its first day (see The Dot-com Bubble; Akamai was one of the survivors that had revenue attached to its physics).

Danny Lewin (an Israeli-American who had served in Sayeret Matkal, the IDF’s elite commando unit, before MIT) was Akamai’s technical soul. On the morning of September 11, 2001, aged 31, he boarded American Airlines Flight 11. Seated closest to the hijackers, he is believed to have fought them and been stabbed, quite possibly the first victim of 9/11. That same morning, Akamai’s network did exactly what it was built for: as the world hit refresh, news sites that would have collapsed alone stayed reachable on the strength of the edge network Lewin had built. Leighton, his co-founder and mentor, became CEO in 2013 and still runs the company: ~365,000 servers in 135+ countries, long since expanded from delivery into security.

What a CDN Actually Does

The trick generalizes far beyond caching images. A CDN terminates the user’s connection near the user (cutting TCP/TLS round trips), caches whatever is cacheable, races the rest over optimized backbone routes, absorbs DDoS attacks across its whole capacity (a flood that would kill any single site is background noise across hundreds of terabits of edge; see Cybersecurity: The Invisible War), and increasingly runs code at the edge. Video made CDNs load-bearing for culture: streaming is delivery, and the Streaming Wars run on it: Netflix built its own private CDN, Open Connect, placing its catalog inside ISPs worldwide rather than pay anyone else to. Amazon’s CloudFront (2008) bundled delivery into the cloud; Fastly (2011) rebuilt the idea around instant purge and edge programmability for the API era.

Cloudflare: The CDN as Mass Utility

Cloudflare (founded July 2009 by Matthew Prince, Michelle Zatlyn, and Lee Holloway, out of the Project Honey Pot anti-spam effort; launched September 2010) inverted Akamai’s enterprise economics: a free tier for anyone, reverse-proxying whole sites, with security (the “firewall in the cloud”) as the product. It worked at internet scale: by the mid-2020s Cloudflare fronted roughly a fifth of all websites. Ubiquity bought it a permanent seat in the content-moderation wars: having long argued infrastructure should be neutral, Cloudflare nonetheless dropped the Daily Stormer (2017), 8chan (2019, after El Paso), and Kiwi Farms (2022) under public pressure, each time with a public essay agonizing that an infrastructure company deciding who may exist online is a power nobody should want (see Content Moderation). The edge also became a compute platform: Cloudflare Workers and its rivals moving application logic into the delivery layer itself, the CDN completing its evolution from cache to distributed operating system for the web.

⚠️ The Centralization Paradox

The CDN was invented to remove single points of failure; concentration reinvented them. On June 8, 2021, one customer’s configuration triggered a latent bug at Fastly and, for under an hour, took down Reddit, Amazon, gov.uk, and much of the world’s press, one company, one bug, front pages everywhere. Cloudflare’s own stumbles (2019, 2020, 2022, and a pair of major outages in late 2025 that returned mass 500 errors across X, ChatGPT, Spotify, and thousands of others) each produced the same headline: half the internet is down. It never is, but the visible web increasingly shares four or five front doors, and a fault in any one of them is a synchronized global event. The economics that centralized delivery (peering leverage, DDoS arms races, free tiers only giants can fund) are the same that centralized the cloud; the resilience story of the internet (packet switching routing around damage) quietly inverted at the application layer. The first generation of CDN competitors (Digital Island, Sandpiper, Exodus) died in the dot-com crash; the survivors became so essential that their outages are now measured in fractions of global GDP per minute. Redundancy exists (multi-CDN setups are standard for those who can afford them) but the web’s default remains: one edge provider, configured once, trusted absolutely.

Fun Fact

Tom Leighton never stopped being an MIT mathematics professor; he is likely the only person to run a multibillion-dollar public company while holding a professorship in applied mathematics, and Akamai remains the most valuable company ever built directly on a STOC theory paper. Consistent hashing, the 1997 result behind it, now also underpins Amazon’s Dynamo, Cassandra, and virtually every distributed cache on Earth, and has become a standard software-engineering interview question, asked daily at companies that exist because of it.

📚 Sources