The History of Content Delivery Networks (CDN)

Shalom Carmel Chief Information Officer at GlobalDots
3 Min read

Although Content Delivery Network (CDN) is to reveal all of its true power in the future decades, an insight into how it came to be is quite useful. CDNs are surrogate web servers distributed across different data centers in different geographical regions to deliver content to end-users, based on proximity of this user. Thus, using a CDN hosting system instead of a standard one, offers a cost-effective solution for an online vendor, or an e-commerce owner, to keep his impatient customers satisfied.

It also means the faster performance of a hosted website and a better security from hacker attacks. This is because CDNs maintain multiple Points of Presence, i.e. servers store copies of identical content and and apply a mechanism that provides logs and information to the origin servers. Instead of a standard client-server communication, two communication flows are used. Between client and the surrogate server, and then between the surrogate server and the origin server.

Book a demo today to see GlobalDots is action.

Optimize cloud costs, control spend, and automate for deeper insights and efficiency.

Book a demo today to see GlobalDots is action.
A network diagram illustrating multiple servers connected to client computers through a central cloud structure.

Source: https://en.wikipedia.org/wiki/Content_delivery_network

To sum it up, CDNs keep:

  • the Internet less clogged
  • the Web customers more satisfied
  • the e-commerce business more cost-effective

CDNs Through Generations

The development of content delivery networks sought to deal with extreme bandwidth pressures, first as video streaming was growing in demand as well as the number of content providers. That was in the past. Now, CDNs are a continual trend, with the emergence of cloud computing, involving all the layers of cloud computing:

  • SaaS (Software as a service), e.g. Google Docs
  • IaaS (Infrastructure as a service), e.g. Amazon
  • PaaS (Platform as a service) e.g. Google App Engine
  • BPaaS (Business Process as a service) e.g. advertisements, payments
Diagram illustrating different cloud service models and management responsibilities.

Source: VentureBeat

The first generation CDNs were not encountered before the late 90’s. However, some technological innovations that preceded this generation of CDNs, such as server farms, hierarchical caching, caching proxy deployment and so on, were crucial for paving the ground of the desired infrastructure of such internet un-clogging technology.

First Generation CDNs were designed to address the higher demand for audio and video streaming, to accelerate websites, to support growing volumes of content. Finally to enable the companies providing products or services to handle all requests from the Internet users, and still not face a significant loss in revenue while dealing with their IT infrastructure.

The main focus of a second generation CDNs however was a peer to peer production, cloud computing and energy awareness. Also, serving the demand of the internet crowd for more – interactivity. And not only from their desktop browser, but also their mobile devices. Also, many many ISPs, telcos, IT companies and traditional broadcasters spread across the globe. Some moved into the CDN industries themselves (Amazon, AT&T).

The third generation CDNs are expected to be completely community driven. Autonomous and self-manageable. Its main focus, the quality of experience for the end-user.

Some Historical Events that Speeded Up the Development of CDN technologies

  • 9/11 Terrorist attack: a sudden, unanticipated mass of Internet users tried to access the particular news site, simultaneously. This caused severe caching problems, and finally more money invested in developing CDN hosting to provide protection from the flash crowds for the websites
  • Akamai Technologies evolved out of an MIT research effort aimed at solving the flash crowd problem
  • Broadband Services Forum (BSF), ICAP forum, Internet Streaming Media Alliance organizations all took initiatives to develop standards for delivering broadband content, streaming rich media content – video, audio, and associated data – over the Internet
  • By 2002, large-scale ISPs started building their own CDN functionality, providing customized services
  • In 2004, more than 3000 companies were found to use CDNs, spending more than $20 million monthly
  • In 2005, CDN revenue for both streaming video and Internet radio was estimated to grow at 40%
  • Combined commercial market value for streaming audio, video, streaming audio and video advertising, download media and entertainment was estimated at between $385 million to $452 million in 2005
  • In 2008 Amazon launched their Content Delivery Network
  • In 2011 AT&T announces their new cloud-based Content Delivery Network that enables content to flow from its 38 data centers around the world to reduce transit and latency times
  • In May 2011, Google said it had 200,000 active applications and 100,000 active developers.
  • The stocks of leading CDN market players (Akamai, Limelight, EdgeCast) slumped; Akamai’s total revenue for 2011 was $1,159 million, a 13% increase over 2010 revenue of $1,024 million
  • Akamai’s stock revenue for 2012 is reported to be $345.32 million
  • Cisco projected 2012 Video CDN revenues at around $1 billion with growth for 2013 between 40% and 45%, and the complete market to grow from $6 billion to $12 billion by 2015.
Advertisement promoting a free trial for a Content Delivery Network (CDN) without requiring a credit card.

Latest Articles

What is an API Security Audit?

 In January 2024, a misconfigured API exposed 650,000 private messages. These included passwords and internal communications. No exploit chain. No zero-day. Just a public-facing endpoint with no authentication. This wasn’t an isolated incident. From T-Mobile and Twitter (now X) to Kronos Research and the US Treasury, attackers have consistently used APIs as entry points. They […]

Ganesh The Awesome
26th June, 2025
The Ultimate API Security Checklist for 2025

APIs are now the top attack vector in enterprise apps. In 2024 alone, breaches tied to APIs cost an average of $4.88 million, and that number is rising fast. Attackers exploit gaps in API authentication, input validation, and outdated endpoints to compromise systems. Legacy controls no longer suffice, and the OWASP API Top 10 outlines […]

Ganesh The Awesome
26th June, 2025
10 API Security Best Practices for 2025

APIs are the backbone of today’s interconnected software. They power everything from mobile apps and SaaS platforms to internal microservices and partner integrations. But their rapid growth has left many security teams flat-footed. In 2025, many attackers prefer to exploit API misconfigurations hiding in plain sight. What used to be fringe cases (token leakage, zombie […]

Ganesh The Awesome
23rd June, 2025
API Security in 2025: Practical Assessment & Modern Protection Strategies

APIs are no longer an edge case. In 2025, they’re a core requirement for maintaining trust, compliance, and operational continuity. As organizations build more API-driven systems—from customer apps to internal microservices—the exposure risk compounds. And quickly, too. Even mature security teams are finding that traditional tools can’t keep pace with the volume, velocity, and nuance […]

Ganesh The Awesome
23rd June, 2025

Unlock Your Cloud Potential

Schedule a call with our experts. Discover new technology and get recommendations to improve your performance.

    GlobalDots' industry expertise proactively addressed structural inefficiencies that would have otherwise hindered our success. Their laser focus is why I would recommend them as a partner to other companies

    Marco Kaiser
    Marco Kaiser

    CTO

    Legal Services

    GlobalDots has helped us to scale up our innovative capabilities, and in significantly improving our service provided to our clients

    Antonio Ostuni
    Antonio Ostuni

    CIO

    IT Services

    It's common for 3rd parties to work with a limited number of vendors - GlobalDots and its multi-vendor approach is different. Thanks to GlobalDots vendors umbrella, the hybrid-cloud migration was exceedingly smooth

    Motti Shpirer
    Motti Shpirer

    VP of Infrastructure & Technology

    Advertising Services