Akamai Technologies was incorporated to turn MIT research on distributed content delivery into a business. This helped formalize the idea that moving content closer to users could make the web faster and more reliable. Akamai became an early, influential model for commercial content delivery networks (CDNs).
The IETF published HTTP/1.1, which clarified how web requests, responses, and caching should work. Better-defined caching rules made it easier to build systems that reuse content safely instead of refetching it repeatedly. These protocol basics supported the growth of proxy caches and CDNs as the web scaled.
Akamai’s IPO brought major public attention to content delivery as a fast-growing part of internet infrastructure. The strong market reception signaled that performance and reliability problems on the web were large enough to support specialized global delivery networks. This moment helped validate CDNs as a distinct infrastructure layer.
AWS introduced Amazon CloudFront, offering CDN capabilities through an on-demand, pay-as-you-go model. This made global edge caching accessible through APIs and cloud tooling, not just custom enterprise contracts. It tied content delivery more closely to cloud platforms and developer workflows.
Cloudflare was founded to provide a network service that sits between sites and visitors, improving speed while also filtering attacks. This reflected a broader shift: edge networks were becoming security enforcement points, not just caches for static files. Over time, this blended “CDN” and “security” into a single platform model.
Cloudflare announced its public launch at TechCrunch Disrupt, promoting simple setup for performance and protection features. This lowered the barrier for smaller sites to use an “edge” service that previously required deep networking expertise. It helped expand edge infrastructure use beyond large enterprises.
Netflix announced Open Connect, a dedicated CDN designed to deliver Netflix video more efficiently. Rather than relying only on third-party CDNs, Netflix offered ISPs choices like peering or installing caching appliances closer to viewers. This showed how large content providers could build private edge delivery systems at global scale.
The IETF published RFC 7230, part of a major update that clarified and reorganized HTTP/1.1 specifications. Cleaner, more precise definitions helped implementers build more consistent proxies, gateways, and caching layers. This kind of protocol maintenance mattered as CDNs and edge services handled more of the world’s web traffic.
HTTP/2 was published to reduce latency by allowing many requests over one connection and compressing headers. These changes improved page-load performance, especially on modern, resource-heavy websites. CDNs played a key role in deployment because they could add HTTP/2 support at the edge for many customer sites at once.
Let’s Encrypt opened its public beta so anyone could request free TLS certificates. This helped remove cost and manual work as major barriers to encrypting websites. Wider HTTPS adoption pushed CDNs and edge providers to scale automated certificate management and encrypted traffic handling.
Cloudflare announced general availability of Workers, letting developers run code on Cloudflare’s global network instead of only in centralized data centers. This marked a clear shift from “edge caching” to “edge computing,” where business logic can run close to users. It expanded what CDNs could do: not just deliver content, but execute applications at the edge.
The IETF published TLS 1.3, updating how secure connections are negotiated. TLS 1.3 reduced handshake complexity and removed older, weaker options, helping security and often improving connection setup time. Edge networks benefited because they terminate and manage large volumes of encrypted sessions for many sites.
Content Delivery Networks and the Rise of Edge Infrastructure (1998–2020)