Server Selection Mechanism. Server Selection Policy. Content Distribution Network. Content Distribution Networks. Proactive content replication

Similar documents
CONTENT-DISTRIBUTION NETWORKS

CSE 124: CONTENT-DISTRIBUTION NETWORKS. George Porter December 4, 2017

Content Distribu-on Networks (CDNs)

Mul$media Networking. #9 CDN Solu$ons Semester Ganjil 2012 PTIIK Universitas Brawijaya

11/13/2018 CACHING, CONTENT-DISTRIBUTION NETWORKS, AND OVERLAY NETWORKS ATTRIBUTION

Web, HTTP, Caching, CDNs

CSE 486/586 Distributed Systems

416 Distributed Systems. March 23, 2018 CDNs

CSE 123b Communications Software

Today s class. CSE 123b Communications Software. Telnet. Network File System (NFS) Quick descriptions of some other sample applications

HTTP and Web Content Delivery

Content Distribution. Today. l Challenges of content delivery l Content distribution networks l CDN through an example

Venugopal Ramasubramanian Emin Gün Sirer SIGCOMM 04

Introduction to Computer Networks

Outline Computer Networking. HTTP Basics (Review) How to Mark End of Message? (Review)

CS 43: Computer Networks. 14: DHTs and CDNs October 3, 2018

Distributed Systems. 21. Content Delivery Networks (CDN) Paul Krzyzanowski. Rutgers University. Fall 2018

CS November 2018

The Design and Implementation of a Next Generation Name Service for the Internet (CoDoNS) Presented By: Kamalakar Kambhatla

Files/News/Software Distribution on Demand. Replicated Internet Sites. Means of Content Distribution. Computer Networks 11/9/2009

How Akamai delivers your packets - the insight. Christian Kaufmann SwiNOG #21 11th Nov 2010

Content Delivery on the Web: HTTP and CDNs

Distributed Systems. Distributed Systems Within the Internet Nov. 9, 2011

CS November 2017

CSE 124: TAIL LATENCY AND PERFORMANCE AT SCALE. George Porter November 27, 2017

Last Class: Consistency Models. Today: Implementation Issues

Mul$cast and Anycast. Outline today TODAY 3/11/14. Mike Freedman COS 461: Computer Networks. IP Anycast

Overview Computer Networking Lecture 16: Delivering Content: Peer to Peer and CDNs Peter Steenkiste

EECS 122: Introduction to Computer Networks DNS and WWW. Internet Names & Addresses

TAIL LATENCY AND PERFORMANCE AT SCALE

Today: World Wide Web! Traditional Web-Based Systems!

CS 43: Computer Networks BitTorrent & Content Distribution. Kevin Webb Swarthmore College September 28, 2017

CS519: Computer Networks. Lecture 6: Apr 5, 2004 Naming and DNS

TECHNISCHE UNIVERSITEIT EINDHOVEN Faculteit Wiskunde en Informatica

IP ADDRESSES, NAMING, AND DNS

Drafting Behind Akamai (Travelocity-Based Detouring)

ThousandEyes for. Application Delivery White Paper

Table of Contents 1 DNS Configuration 1-1

Internet Anycast: Performance, Problems and Potential

Protecting DNS from Routing Attacks -Two Alternative Anycast Implementations

Computer Networks. Wenzhong Li. Nanjing University

Internet Content Distribution

0 0& Basic Background. Now let s get into how things really work!

Communications Software. CSE 123b. CSE 123b. Spring Lecture 11: Domain Name System (DNS) Stefan Savage. Some pictures courtesy David Wetherall

CSE 123b Communications Software. Overview for today. Names and Addresses. Goals for a naming system. Internet Hostnames

ANYCAST and MULTICAST READING: SECTION 4.4

Turbo King: Framework for Large- Scale Internet Delay Measurements

Democratizing Content Publication with Coral

Authors: Rupa Krishnan, Harsha V. Madhyastha, Sridhar Srinivasan, Sushant Jain, Arvind Krishnamurthy, Thomas Anderson, Jie Gao

Chapter 3: Naming Page 38. Clients in most cases find the Jini lookup services in their scope by IP

Democratizing Content Publication with Coral

SaaS Providers. ThousandEyes for. Summary

Lecture 16: Router Design

The term "router" in this document refers to both routers and Layer 3 switches. Step Command Remarks. ipv6 host hostname ipv6-address

Domain Name System.

Configuring IPv6 DNS. Introduction to IPv6 DNS. Configuring the IPv6 DNS client. Configuring static domain name resolution

Yet another redirection mechanism for the World-Wide Web?

CS4/MSc Computer Networking. Lecture 3: The Application Layer

Naming and Content Distribution

Scaling Internet TV Content Delivery ALEX GUTARIN DIRECTOR OF ENGINEERING, NETFLIX

Flooded Queries (Gnutella) Centralized Lookup (Napster) Routed Queries (Freenet, Chord, etc.) Overview N 2 N 1 N 3 N 4 N 8 N 9 N N 7 N 6 N 9

Computer Networks. More on Standards & Protocols Quality of Service. Week 10. College of Information Science and Engineering Ritsumeikan University

Homework 3 1 DNS. A root. A com. A google.com

CS 344/444 Computer Network Fundamentals Final Exam Solutions Spring 2007

Chapter 6: Distributed Systems: The Web. Fall 2012 Sini Ruohomaa Slides joint work with Jussi Kangasharju et al.

Understanding and Characterizing Hidden Interception of the DNS Resolution Path

The Application Layer: Sockets, DNS

Configuring Answers and Answer Groups

Configuring Answers and Answer Groups

Finding a Needle in a Haystack. Facebook s Photo Storage Jack Hartner

CSC2231: DNS with DHTs

Local Area Networks; Ethernet

Consistency and Replication. Why replicate?

Department of Computer Science Institute for System Architecture, Chair for Computer Networks. Caching, Content Distribution and Load Balancing

I. Announcments II. What does ICANN (Internet Corporation for Assigned Names and Numbers) do? a. Draws up a contract with each registry b.

CS 347 Parallel and Distributed Data Processing

OASIS: Anycast for Any Service

DNS and CDNs : Fundamentals of Computer Networks Bill Nace

CS 347 Parallel and Distributed Data Processing

Large-Scale Web Applications

Today: World Wide Web

D-mystifying the D-Root Address Change

CE693: Adv. Computer Networking

Electronic Mail. Three Components: SMTP SMTP. SMTP mail server. 1. User Agents. 2. Mail Servers. 3. SMTP protocol

Today: World Wide Web. Traditional Web-Based Systems

The Google File System (GFS)

Distributed Naming. EECS 591 Farnam Jahanian University of Michigan. Reading List

Network Security Part 3 Domain Name System

Communication Networks

End-user mapping: Next-Generation Request Routing for Content Delivery

CSE561 Naming and DNS. David Wetherall

Lecture 6: Overlay Networks. CS 598: Advanced Internetworking Matthew Caesar February 15, 2011

For the sake of entirety I would like to mention the main differences between a), b), and c) architectures.

Performance Analysis for Crawling

Internet Load Balancing Guide. Peplink Balance Series. Peplink Balance. Internet Load Balancing Solution Guide

CISC 7610 Lecture 5 Distributed multimedia databases. Topics: Scaling up vs out Replication Partitioning CAP Theorem NoSQL NewSQL

CSEN 404 Introduction to Networks. Mervat AbuElkheir Mohamed Abdelrazik. ** Slides are attributed to J. F. Kurose

NetServ: Dynamically Deploying In-network Services

BGP. Daniel Zappala. CS 460 Computer Networking Brigham Young University

Domain Name System (DNS)

Transcription:

Content Distribution Network Content Distribution Networks COS : Advanced Computer Systems Lecture Mike Freedman Proactive content replication Content provider (e.g., CNN) contracts with a CDN CDN replicates the content On many servers spread throughout the Internet Updating the replicas Updates pushed to replicas when the content changes CDN server in S. America origin server in North America CDN distribution node CDN server in Europe CDN server in Asia Server Selection Policy Server Selection Mechanism Live server For availability Lowest load To balance load across the servers Closest Nearest geographically, or in round-trip time Best performance Throughput, latency, Requires continuous monitoring of liveness, load, and performance Cheapest bandwidth, electricity, Application redirection GET Redirect GET OK Advantages Fine-grain control Selection based on client IP address Disadvantages Extra round-trips for TCP connection to server Overhead on the server

Server Selection Mechanism Routing Anycast routing...0/...0/ Advantages No extra round trips Route to nearby server Disadvantages Does not consider network or server load Different packets may go to different servers Used only for simple request-response apps DNS query Server Selection Mechanism Naming DNS-based server selection local...... A DNS lookup traverses DNS hierarchy DNS caching Client. (root) authority..0. edu.: NS...0 com.: NS... io.: NS..00. Contact...0 for edu. www.princeton.edu A 0.0.. Local nameserver. (root): NS..0. edu.: NS...0 princeton.edu.: NS..0. edu. authority...0 princeton.edu.: NS..0. pedantic.edu.: NS... Contact..0. for princeton.edu. princeton.edu. authority..0. www.princeton.edu.: A 0.0.. www.princeton.edu.: A 0.0.. Performing all these queries takes time And all this before actual communication takes place Caching can greatly reduce overhead Top-level servers very rarely change, popular sites visited often Local often has information cached How DNS caching works All s cache responses to queries Responses include a time-to-live (TTL) field, akin to cache expiry

Server Selection Mechanism DNS query Naming DNS-based server selection local...... Advantages Avoid TCP set-up delay DNS caching reduces overhead Relatively fine control Disadvantage Based on IP address of local Hidden load effect DNS TTL limits adaptation How Works 0 How Uses DNS How Uses DNS DNS root server GET index. html http://cache.cnn.com/foo.jpg global regional DNS lookup cache.cnn.com ALIAS: g.akamai.net global regional

How Uses DNS How Uses DNS DNS lookup g.akamai.net global ALIAS a.g.akamai.net t ai.ne kam a. g. a DNS Address... regional global regional How Uses DNS How Uses DNS GET foo.jpg global regional GET /foo.jpg Host: cache.cnn.com global regional GET /foo.jpg Host: cache.cnn.com

How Uses DNS How Works: Cache Hit global regional global regional 0 Mapping System Equivalence classes of IP addresses IP addresses experiencing similar performance Quantify how well they connect to each other Collect and combine measurements Ping, traceroute, BGP routes, server logs E.g., over 00 TB of logs per days Network latency, loss, and connectivity Mapping System Map each IP class to a preferred server Based on performance, health, etc. Updated roughly every minute Map client request to a server in the Load balancer selects a specific server E.g., to maximize the cache hit rate 0

Adapting to Failures Failing hard drive on a server Suspends after finishing in progress requests Failed server Another server takes over for the IP address Low-level map updated quickly Failed High-level map updated quickly Failed path to customer s origin server Route packets through an intermediate node Conclusion Content distribution is hard Many, diverse, changing objects Clients distributed all over the world Reducing latency is king Contribution distribution solutions Reactive caching Proactive content distribution networks