Content Distribution

Networks
Presented by
Md. Rahat Hasan  Submitted To
ID: B160305019 Sajeeb Saha
Assistant Professor
Wahida Ferdose Urmi  Department Of CSE, Jagannath University
ID: B150305035

1
Contents
 Introduction
 Single Data Center
 Content Distribution Networks
How does a CDN work?
 Server Placements Philosophies
 Cluster Selection Strategies
Case Study-Netflix
Case Study- Youtube
Case Study- Kankan

2
Introduction
Internet video companies are distributing on-demand multi-Mbps streams to millions
of users on a daily basis.

Challenge: How to stream content to millions of simultaneous users all over the
world?

 Option 1: Single, large massive data center (Without a CDN)

 Option 2: Content Distribution Networks (CDN)

3
 Single Data Center
 Store all of its videos in the data center

 Stream the videos directly from the data center to clients worldwide

 Drawbacks:
 Long latency

 Easy to be overloaded

 Single point of failure

 Waste of network bandwidth

4
Without A
CDN

5
Without A CDN
If user from a similar or other location tries to access the same site, he will go
through the same sequence.

 User requests will hit the origin and the origin will reply with content. Each
step along the way adds a delay, or “latency”.

 If the origin is located far from the user, response times will suffer from
significant latency, delivering a poor user experience.

6
Content Distribution Networks
 CDN stands for content delivery network or content distribution network (CDN) is a

highly-distributed platform of servers distributed geographically around the world

 Stores copies of videos

 Web contents (including documents, images and audios).

The goal of a CDN is to serve content to end-users with-

 High availability

 High performance.

7
Contents of CDN
 CDNs serve a large fraction of the Internet content today, including:

 web objects (text, graphics and scripts)

 downloadable objects (media files, software, documents)

 applications (e-commerce, portals)

 live streaming media

 on-demand streaming media

 social networks.

8
Types of CDN
 Private CDN
 When 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.
 Example: Google’s CDN distributes YouTube videos and other types of
content
 Third-party CDN
 Distributes content on behalf of multiple content providers
 Example: Akamai’s CDN distributes Netflix and Hulu contents, among
others.

9
How Does A CDN Work?
 CDNs work by reducing the physical distance between a user and the origin (a web
or an application server).

 It involves a globally distributed network of servers that store content much closer to
the client than the origin.

CDN architecture provides the ability to optimize content in 2 separate ways - Pull
Zones and Push Zones.

10
 Pull Zone & Push Zone
Pull Zone automatically pulls the content from Push Zone on the other hand, places uploaded
origin server and creates a copy that will be content on various storage servers across the
served to users. globe and pushes content to the POP upon user
request.

11
With CDN

12
With vs
Without CDN

13
 1. Bob gets URL for for video
http://netcinema.com/6Y7B23V
from netcinema.com 2. resolve http://netcinema.com/6Y7B23V

Example Of web page

1
2 via Bob’s local DNS
5 4&5. Resolve

CDN
6. request video from
http://KingCDN.com/NetC6y&B23
KINGCDN server,
via KingCDN’s authoritative DNS,
streamed via HTTP which returns IP address o

Operation netcinema.com 3. netcinema’s DNS returns URL

http://KingCDN.com/NetC6y&B23V 4
KIingCDN
server with video

netcinema’s
authorative DNS KingCDN.com KingCDN
authoritative DNS 14
Services of CDN
 Request redirection and content delivery services
 direct a request to the closest suitable CDN cache server

 Content outsourcing and distribution services

 replicate and/or cache content from the origin server to distributed Web
servers.

 Content negotiation services

 meet specific needs of each individual user (or group of users).
15
Server Placements Philosophies
 Enter Deep

 it is introduced by Akamai.

 It deploys server clusters in access ISPs (ISPs direct accessing end users) all over the
world approximately at 17,000 locations.

 Its primary goal is to serve the end users effectively

 decreasing the number of routers and

 links between CDN server and the end user.

16
Server Placements Philosophies
 Bring home

 It can be taken by Limelight and other CDN companies

 It brings the ISPs home by building large clusters at a smaller number of key
locations and connecting these clusters using a private high-speed network.

CDNs can place the clusters at Internet Exchange Points (IXPs).

Maintenance and management results in lower when compared with the Enter Deep.

It may result in lower throughput and higher delay.

17
Case Study - GOOGLE’S NETWORK
INFRASTRUCTURE
 To support its vast array of cloud services—including search, gmail, calendar, YouTube video,

maps, documents, and social networks—Google has deployed an extensive private network and
CDN infrastructure.

 Google’s CDN infrastructure has three tiers of server clusters:

Eight “mega data centers,” with six located in the United States and two located in Europe

About 30 “bring-home” clusters , with each cluster consisting on the order of 100–500
servers.

Many hundreds of “enter-deep” clusters, with each cluster located within an access ISP

18
Cluster Selection Strategies
 Mechanism for dynamically directing clients to a server cluster or a data center within the
CDN.
 Geographically closest.

 Real-time measurements

 IP anycast

 Factors:
 Delay, loss , bandwidth performance of network

 Load on the clusters

 ISP delivery cost

19
Geographically Closest
 Assign the client to the cluster that is geographically closest.
 Using commercial geo-location databases, each LDNS IP address is mapped to a
geographic location.
 When a DNS request is received from a particular LDNS, the CDN chooses the
geographically closest cluster
 Several drawbacks: -
 Closest geographically does not mean closest in network terms (i.e path)
 May not be a good choice with remote local DNS servers
 Network dynamics not taken into account

20
Real-time Measurements
 Determine the best cluster for a client based on the current traffic conditions

 Measure delay and loss between their clusters and clients

 Active measurement of delay and loss through dedicated (for example, ping messages or DNS
queries)

 One drawback of this approach is that many LDNSs are configured to not respond to such
probes.

 Passive monitoring of recent/ongoing traffic between clients and CDN servers (observing
delay estimated by examining the gap between server-to-client SYNACK and client-to-server
ACK during the TCP three-way handshake)
21
IP anycast
 The routers in the Internet route the client's packet to the “closest” cluster, as determined by
BGP.

 Same IP address appearing in multiple clusters

 BGP router treats receives multiple route advertisements as different paths to the same
physical location.

 BGP router will then pick the “best” route to the IP address according to its route selection
mechanism.

22
IP anycast
 Benefits:
 Simple, high performance

 Find best route

 Disadvantages:
 Possibility of overload

 Ignores dynamic characteristics of network

23
Case Study - Netflix
Leading service provider for online movies and TV
shows

Netflix Open Connect is a Content Delivery Network

(CDN) generating almost 30 percent of the downstream
U.S. Internet traffic in 2011.

Use third-party cloud services and CDNs extensively.

Netflix employs video distribution using a CDN (actually

multiple CDNs) and adaptive streaming over HTTP

24
Architectural Components
 The registration and payment servers
 Netflix maintains registration and payment servers in its own hardware infrastructure

 The Amazon cloud

 Netflix runs its online service by employing machines (or virtual machines) in the Amazon
cloud. Some of the functions taking place in the Amazon cloud include:

• Content ingestion.

• Content processing

• Uploading versions.

25
Architectural Components
 Multiple CDN providers
 To deliver the movies to its customers on demand, Netflix makes extensive use of CDN technology.

Netflix employs not one but three third-party CDN companies at the same time

• Akamai

• Limelight

• Level-3.

 Clients

26
 upload copies of
Amazon cloud
multiple versions of
video to CDNs Akamai CDN

Netflix Netflix registration,

accounting servers
3. Manifest file

Basic 2. Bob browses

Netflix video 2
returned for
requested video Limelight
CDN
Architecture 1
3

1. Bob manages
Netflix account
Level-3 CDN
4. DASH
streaming

27
 Case Study - YouTube
 A globally popular “user-generated” (short) video
sharing site

 Approximately half a billion videos in its library and

half a billion video views per day

 YouTube started its journey in April 2005 and was

acquired by Google in November 2006.

 Google uses its own private CDN to distribute

YouTube videos.

28
YouTube Architecture before Google
 Three (logical) web servers
 Located near San Jose, CA

 Seven data centers consisting of thousands of flash video servers

 located across continental US only

 Use Limelight CDN to help video distribution

29
 YouTube Video Delivery Architecture
 YouTube videos streamed from server to client over
HTTP .
 YouTube uploaders upload their videos from client to
server over HTTP.
 YouTube processes video it receives, convert it to a
YouTube video format and create multiple versions at
different bit rates.
 Google runs YouTube service within its own vast
infrastructure of data centers, private CDN, and private YouTube Backend
global network.

30
YouTube Video Delivery
 Google has installed server clusters in many hundreds of different locations.

 From a subset of about 50 of these locations, Google distributes YouTube videos

 Uses DNS to redirect a customer request to a specific cluster

 Directs the client to the cluster for which the RTT between client and cluster is the lowest;

 To balance the load across clusters, the client is directed (via DNS) to a more distant cluster

 If a cluster does not have the requested video, the cluster return an HTTP redirect message,
and redirecting the client to another cluster

31
Case Study - Kankan
 P2P-based video-on demand provider in China

 It has over 30 million unique users per month

 Used for making less traffic and less infrastructure

 Avoids CDN by reducing its infrastructure and bandwidth costs

 Similar to BitTorrent

32
Kankan
 When a peer wants to see a video it
 Contacts a tracker (centralized or peer-based DHT)

 The peer then requests chunks of the video file in parallel from the other peers that have the
file.

Requests are preferentially made for the chunks to be viewed in near future .

Swarms of 10,000+ peers for popular videos

Recently added a CDN for initial loading of video and as a fallback if P2P download rate is too
slow

33
Kankan
Architecture

Fig. Hybrid CDN-P2P VoD streaming architecture of Kankan.

34
Advantages of CDN
 Lower server load.

 Reducing bandwidth costs

 Faster content delivery to the web browsers.

 Improving website security

 Increasing content availability

35
Disadvantages of CDN
Content delivery networks cost additional money.

 Adds complexity to website and deployment procedures.

 Customers may have network filters that block some Content

delivery networks and prevent content from being loaded.

36
References
[1]. COMPUTER NETWORKING-A Top-Down Approach Sixth Ed. By James F. Kurose &
Keith W. Ross
[2]. https://www.cdnetworks.com/what-is-a-cdn/
[3]. Unreeling Xunlei Kankan: Understanding Hybrid CDN-P2P Video-on-Demand Streaming
Ge Zhang, Wei Liu, Member, IEEE, Xiaojun Hei, Member, IEEE, and Wenqing Cheng, Member,
IEEE
[4]. Content Delivery Networks: State of the Art, Insights, and Imperatives
Mukaddim Pathan, Rajkumar Buyya and Athena Vakali

37
 Thank
YOU !!!

38