Content delivery network

CDN nodes are usually deployed in multiple locations, often over multiple Internet backbones. Benefits include reducing bandwidth costs, improving page load times, and increasing the global availability of content. The number of nodes and servers making up a CDN varies, depending on the architecture, with some reaching thousands of nodes with tens of thousands of servers on many remote points of presence (PoPs). Others build a global network and have a small number of geographical PoPs.

Requests for content are typically algorithmically directed to nodes that are optimal in some way. When optimizing for performance, locations that are best for serving content to the user may be chosen. This may be measured by choosing locations that are the fewest hops or the shortest time to the requesting client, or the highest server performance, to optimize delivery across local networks. When optimizing for cost, locations that are the least expensive may be chosen instead. In an optimal scenario, these two goals tend to align, as edge servers that are close to the end user at the edge of the network may have an advantage in performance and cost.

Most CDN providers will provide their services over a varying, defined set of PoPs, depending on the coverage desired, such as the United States, Asia-Pacific, International or Global, etc. These sets of PoPs can be called "edges", "edge nodes", "edge servers", or "edge networks" as they would be the closest edge of CDN assets to the end user.

CDN concepts:

• Content Provider Origin Server: the web server providing the source content
• CDN entry point(s): the servers within the CDN that fetch the content from the origin
• CDN Origin Shield: the CDN service helping to protect the origin server in case of heavy traffic
• CDN Edge Servers: the CDN servers serving the content request from the clients
• CDN footprint: the geographic areas where the CDN Edge Servers can effectively serve clients' requests
• CDN selector: in the context of multi-CDN, a decision-making service to choose among multiple CDNs
• CDN offloading: in the context of Peer-to-Peer CDN, a mechanism to help deliver the content between clients who are consuming it, in addition to CDN Edge Server delivery

CDN providers profit either from direct fees paid by content providers using their network, or profit from the user analytics and tracking data collected as their scripts are being loaded onto customers' websites inside their browser origin. As such these services are being pointed out as potential privacy intrusions for behavioral targeting and solutions are being created to restore single-origin serving and caching of resources.

In particular, a website using a CDN may violate the EU's General Data Protection Regulation (GDPR). For example, in 2021 a German court forbade the use of a CDN on a university website, because this caused the transmission of the user's IP address to the CDN, which violated the GDPR.

CDNs serving JavaScript have also been targeted as a way to inject malicious content into pages using them. Subresource Integrity mechanism was created in response to ensure that the page loads a script whose content is known and constrained to a hash referenced by the website author.

The Internet was designed according to the end-to-end principle. This principle keeps the core network relatively simple and moves the intelligence as much as possible to the network end-points: the hosts and clients. As a result, the core network is specialized, optimized, and simplified to only forward data packets.

Content Delivery Networks extend the transport network by distributing on it a variety of intelligent applications employing techniques designed to optimize content delivery. The resulting tightly integrated overlay uses web caching, server-load balancing, request routing, and content services.

Web caches store popular content on servers that have the greatest demand for the content requested. These shared network appliances reduce bandwidth requirements, reduce server load, and improve the client response times for content stored in the cache. Web caches are populated based on requests from users (pull caching) or based on preloaded content disseminated from content servers (push caching).

Server-load balancing uses one or more techniques, including service-based (global load balancing) or hardware-based (i.e. layer 4-7 switches, also known as a web switch, content switch, or multilayer switch) to share traffic among several servers or web caches. Here the switch is assigned a single virtual IP address. Traffic arriving at the switch is then directed to one of the real web servers attached to the switch. This has the advantage of balancing load, increasing total capacity, improving scalability, and providing increased reliability by redistributing the load of a failed web server and providing server health checks.

A content cluster or service node can be formed using a layer 4-7 switch to balance load across several servers or several web caches within the network.

Request routing directs client requests to the content source best able to serve the request. This may involve directing a client request to the service node that is closest to the client, or to the one with the most capacity. A variety of algorithms are used to route the request. These include Global Server Load Balancing, DNS-based request routing, Dynamic metafile generation, HTML rewriting, and anycasting. Proximity, choosing the closest service node, is estimated using a variety of techniques including reactive probing, proactive probing, and connection monitoring.

CDNs use a variety of methods of content delivery including, but not limited to, manual asset copying, active web caches, and global hardware load balancers.

Content service protocols

Several protocol suites are designed to provide access to a wide variety of content services distributed throughout a content network. The Internet Content Adaptation Protocol (ICAP) was developed in the late 1990s to provide an open standard for connecting application servers. A more recently defined and robust solution is provided by the Open Pluggable Edge Services (OPES) protocol. This architecture defines OPES service applications that can reside on the OPES processor itself or be executed remotely on a Callout Server. Edge Side Includes or ESI is a small markup language for edge-level dynamic web content assembly. It is fairly common for websites to have generated content. It could be because of changing content like catalogs or forums, or because of personalization. This creates a problem for caching systems. To overcome this problem, a group of companies created ESI.

Peer-to-peer CDNs

In peer-to-peer (P2P) content-delivery networks, clients provide resources as well as use them. This means that, unlike client-server systems, the content-centric networks can actually perform better as more users begin to access the content (especially with protocols such as Bittorrent that require users to share). This property is one of the major advantages of using P2P networks because it makes the setup and running costs very small for the original content distributor.

To incentivize peers to participate in the P2P network, web3 and blockchain technologies can be used: participating nodes receive crypto tokens in exchange for their involvement.

Private CDNs

If content owners are not satisfied with the options or costs of a commercial CDN service, they can create their own CDN. This is called a private CDN. A private CDN consists of PoPs (points of presence) that are only serving content for their owner. These PoPs can be caching servers, reverse proxies or application delivery controllers. It can be as simple as two caching servers, or large enough to serve petabytes of content. When a private CDN is deployed within a company network, it is also referred as Entreprise CDN or eCDN.

Large content distribution networks may even build and set up their own private network to distribute copies of content across cache locations. Such private networks are usually used in conjunction with public networks as a backup option in case the capacity of the private network is not enough or there is a failure which leads to capacity reduction. Since the same content has to be distributed across many locations, a variety of multicasting techniques may be used to reduce bandwidth consumption. Over private networks, it has also been proposed to select multicast trees according to network load conditions to more efficiently utilize available network capacity.

Emergence of telco CDNs

The rapid growth of streaming video traffic required large capital expenditures by broadband providers in order to meet this demand and retain subscribers by delivering a sufficiently good quality of experience.

To address this, telecommunications service providers have begun to launch their own content delivery networks as a means to lessen the demands on the network backbone and reduce infrastructure investments.

Telco CDN advantages

Because they own the networks over which video content is transmitted, telco CDNs have advantages over traditional CDNs. They own the last mile and can deliver content closer to the end-user because it can be cached deep in their networks. This deep caching minimizes the distance that video data travels over the general Internet and delivers it more quickly and reliably.

Telco CDNs also have a built-in cost advantage since traditional CDNs must lease bandwidth from them and build the operator's margin into their own cost model. In addition, by operating their own content delivery infrastructure, telco operators have better control over the utilization of their resources. Content management operations performed by CDNs are usually applied without (or with very limited) information about the network (e.g., topology, utilization, etc.) of the telco operators with which they interact or have business relationships. These pose several challenges for the telco operators who have a limited sphere of action in the face of the impact of these operations on the utilization of their resources.

In contrast, the deployment of telco-CDNs allows operators to implement their own content management operations, which enables them to have better control over the utilization of their resources and, as such, provide better quality of service and experience to their end users.

Federated CDNs and Open Caching

In June 2011, StreamingMedia.com reported that a group of TSPs had founded an Operator Carrier Exchange (OCX) to interconnect their networks and compete more directly against large traditional CDNs like Akamai and Limelight Networks, which have extensive PoPs worldwide. This way, telcos are building a Federated CDN offering, which is more interesting for a content provider willing to deliver its content to the aggregated audience of this federation.

It is likely that in the near future, other telco CDN federations will be created. They will grow by enrollment of new telcos joining the federation and bringing network presence and their Internet subscriber bases to the existing ones.

The Open Caching specification by Streaming Video Technology Alliance defines a set of APIs that allows a Content Provider to deliver its content using several CDNs in a consistent way, seeing each CDN provider the same way through these APIs.

Multi CDN and CDN selection

Combining several CDN services allows Content Providers to not rely on a single CDN service, especially concerned to deal with high peak audience during live events. There are several ways to allocate traffic to a particular CDN among the list, either client-side CDN selection, server-side (at the Content Provider's origin), or cloud-side (in the middle, between the content origin and the audience). CDN selection criteria can be performance, availability, and cost.

Improving CDN performance using Extension Mechanisms for DNS

Traditionally, CDNs have used the IP of the client's recursive DNS resolver to geo-locate the client. While this is a sound approach in many situations, this leads to poor client performance if the client uses a non-local recursive DNS resolver that is far away. For instance, a CDN may route requests from a client in India to its edge server in Singapore, if that client uses a public DNS resolver in Singapore, causing poor performance for that client. Indeed, a recent study showed that in many countries where public DNS resolvers are in popular use, the median distance between the clients and their recursive DNS resolvers can be as high as a thousand miles. In August 2011, a global consortium of leading Internet service providers led by Google announced their official implementation of the edns-client-subnet IETF Internet Draft, which is intended to accurately localize DNS resolution responses. The initiative involves a limited number of leading DNS service providers, such as Google Public DNS, and CDN service providers as well. With the edns-client-subnet EDNS0 option, CDNs can now utilize the IP address of the requesting client's subnet when resolving DNS requests. This approach, called end-user mapping, has been adopted by CDNs, and it has been shown to drastically reduce the round-trip latencies and improve performance for clients who use public DNS or other non-local resolvers. However, the use of EDNS0 also has drawbacks as it decreases the effectiveness of caching resolutions at the recursive resolvers, increases the total DNS resolution traffic, and raises a privacy concern of exposing the client's subnet.

Virtual CDN (vCDN)

Virtualization technologies are being used to deploy virtual CDNs (vCDNs) (also known as a software-defined CDN or sd-CDN) to reduce content provider costs, and at the same time, increase elasticity and decrease service delay. With vCDNs, it is possible to avoid traditional CDN limitations, such as performance, reliability, and availability, since virtual caches are deployed dynamically (as virtual machines or containers) in physical servers distributed across the provider's geographical coverage. As the virtual cache placement is based on both the content type and server or end-user geographic location, the vCDNs have a significant impact on service delivery and network congestion.

CDN using non-HTTP delivery

To boost performance, delivery to clients from servers can use alternate non-HTTP protocols such as WebRTC and WebSockets.

Image Optimization and Delivery (Image CDNs)

In 2017, Addy Osmani of Google started referring to software solutions that could integrate naturally with the Responsive Web Design paradigm (with particular reference to the <picture> element) as Image CDNs. The expression referred to the ability of a web architecture to serve multiple versions of the same image through HTTP, depending on the properties of the browser requesting it, as determined by either the browser or the server-side logic. The purpose of Image CDNs was, in Google's vision, to serve high-quality images (or, better, images perceived as high-quality by the human eye) while preserving download speed, thus contributing to a great User experience (UX).

Arguably, the Image CDN term was originally a misnomer, as neither Cloudinary nor Imgix (the examples quoted by Google in the 2017 guide by Addy Osmani) were, at the time, a CDN in the classical sense of the term. Shortly afterwards, though, several companies offered solutions that allowed developers to serve different versions of their graphical assets according to several strategies. Many of these solutions were built on top of traditional CDNs, such as Akamai, CloudFront, Fastly, Edgecast and Cloudflare. At the same time, other solutions that already provided an image multi-serving service joined the Image CDN definition by either offering CDN functionality natively (ImageEngine) or integrating with one of the existing CDNs (Cloudinary/Akamai, Imgix/Fastly).

While providing a universally agreed-on definition of what an Image CDN is may not be possible, generally speaking, an Image CDN supports the following three components:

• A Content Delivery Network (CDN) for the fast serving of images.
• Image manipulation and optimization, either on-the-fly through URL directives, in batch mode (through manual upload of images) or fully automatic (or a combination of these).
• Device Detection (also known as Device Intelligence), i.e. the ability to determine the properties of the requesting browser and/or device through analysis of the User-Agent string, HTTP Accept headers, Client-Hints or JavaScript.

The following table summarizes the current situation with the main software CDNs in this space:

Commercial or free software vendors (build your own CDN)

• Ateme
• BlazingCDN
• Broadpeak
• Gcore
• Go-Fast CDN
• Nginx
• Varnish Software
• Vecima Networks
• Velocix (spin-off Nokia)

Free-as-a-Service

• cdnjs
• Cloudflare
• JSDelivr

Commercial-as-a-Service

• 5centsCDN
• Akamai Technologies
• Alibaba Cloud
• Amazon CloudFront
• Baidu CDN
• BaishanCloud EdgeNext
• BelugaCDN
• Bunny.net
• ByteDance BytePlus
• CacheFly
• CDN77
• CDNetworks (ChinaNetCenter)
• CDNsun
• ChinaCache
• ChinaNetCenter
• Cloudflare
• Comcast Technology Solutions
• EdgeCast Cloud Services (Pulse)
• Fastly
• Gcore
• GlobalConnect
• Google Cloud CDN
• Huawei Cloud
• Jet-Stream Cloud
• KeyCDN
• Kingsoft Cloud
• MainStreaming
• Medianova
• Microsoft Azure Front Door
• Netskrt
• Ngenix
• Ora Streaming (Varnish Software Group)
• OVHcloud
• ProCDN.net
• Qwilt
• Tata Communications
• Tencent Cloud
• Wangsu Science & Technology

Others

• Aryaka
• CenterServ
• Imperva
• INAP
• LeaseWeb
• MetaCDN
• Virtuozzo OnApp CDN
• Rackspace Cloud Files
• Jet-Stream StreamZilla
• Yottaa

Telco CDNs

• AT&T Inc.
• Bharti Airtel
• Bell Canada
• BT Group
• China Telecom
• Chunghwa Telecom
• Deutsche Telekom
• KT
• KPN
• Megafon
• NTT
• Orange CDN
• Pacnet
• PCCW
• Singtel
• SK Broadband
• Tata Communications
• Telecom Argentina
• Telefonica
• Telenor
• TeliaSonera
• Telin
• Telstra
• Telus
• TIM
• Türk Telekom
• Verizon

Commercial using P2P for delivery

• Ace Stream
• Ant Media
• BitTorrent, Inc.
• DLive
• Dolby Milicast
• Goalbit Solutions
• Haivision Teltoo
• Hola SparkCDN
• Livepeer
• Nano Cosmos
• Novage
• PeerFlow
• Peervadoo
• Phenix Real Time Solutions
• Quanteec
• Teleport Media
• Theta EdgeCloud

Multi

• Jet-Stream
• MetaCDN
• NPAW CDN Balancer
• Velocix
• Warpcache

In-house

• TF1
• BBC
• Netflix