{ Content Distribution Networks ECE544 Dhananjay Makwana Principal Software Engineer, Semandex Networks 5/2/14ECE544.

Slides:

Advertisements

Similar presentations

EDNS0 Client-Subnet for DNS based CDNs

Advertisements

1 Server Selection & Content Distribution Networks (slides by Srini Seshan, CS CMU)

1 Content Delivery Networks iBAND2 May 24, 1999 Dave Farber CTO Sandpiper Networks, Inc.

1 Routing and Scheduling in Web Server Clusters. 2 Reference The State of the Art in Locally Distributed Web-server Systems Valeria Cardellini, Emiliano.

19 Historical overview Main challenge: How to distribute content in high quality over the Internet cost-effectively? • Traditional “Best-effort” model:

EEC-484/584 Computer Networks Lecture 6 Wenbing Zhao

Cis e-commerce -- lecture #6: Content Distribution Networks and P2P (based on notes from Dr Peter McBurney © )

An Analysis of Internet Content Delivery Systems Stefan Saroiu, Krishna P. Gommadi, Richard J. Dunn, Steven D. Gribble, and Henry M. Levy Proceedings of.

The Internet Useful Definitions and Concepts About the Internet.

EEC-484/584 Computer Networks Discussion Session for HTTP and DNS Wenbing Zhao

Web Servers How do our requests for resources on the Internet get handled? Can they be located anywhere? Global?

CDNs & Replication Prof. Vern Paxson EE122 Fall 2007 TAs: Lisa Fowler, Daniel Killebrew, Jorge Ortiz.

Anycast Jennifer Rexford Advanced Computer Networks Tuesdays/Thursdays 1:30pm-2:50pm.

1 Drafting Behind Akamai (Travelocity-Based Detouring) AoJan Su, David R. Choffnes, Aleksandar Kuzmanovic, and Fabian E. Bustamante Department of Electrical.

1 Web Content Delivery Reading: Section and COS 461: Computer Networks Spring 2007 (MW 1:30-2:50 in Friend 004) Ioannis Avramopoulos Instructor:

Content Delivery Networks. History Early 1990s sees 100% growth in internet traffic per year 1994 o Netscape forms and releases their first browser.

Technologies for Building Content Delivery Networks Pei Cao Cisco Systems, Inc.

AKAMAI Content Delivery Services AKAMAI Content Delivery Services CIS726 : PRESENTATION Avinash Ponugoti Avinash Ponugoti Nagarjuna Nagulapati Sathish.

Caching and Content Distribution Networks. Web Caching r As an example, we use the web to illustrate caching and other related issues browser Web Proxy.

Content Delivery Networks (CDN) Dr. Yingwu Zhu Reverse Proxy Reverse Proxy Reverse Proxy Intranet Web Cache Architecure Browser Local ISP cache L4 Switch.

Content Distribution Networks (CDNs) Mike Freedman COS 461: Computer Networks Lectures: MW 10-10:50am in Architecture N101

Best Practices in IPv4 Anycast Routing Version 0.9 August, 2002 Bill Woodcock Packet Clearing House.

Content Distribution Network (CDN) Performance Punit Shah CSE581 Internet Technologies OGI, OHSU 2002, Jan 16th.

Information-Centric Networks05a-1 Week 5 / Paper 1 On the use and performance of content distribution networks –Balachander Krishnamurthy, Craig Wills,

A global, public network of computer networks. The largest computer network in the world. Computer Network A collection of computing devices connected.

1 Content Distribution Networks. 2 Replication Issues Request distribution: how to transparently distribute requests for content among replication servers.

Caching and Content Distribution Networks. Some Interesting Observations r Top 1 % of all documents account for 20% - 35% of proxy requests r Top 10%

On the Use and Performance of Content Distribution Networks Balachander Krishnamurthy Craig Wills Yin Zhang Presenter: Wei Zhang CSE Department of Lehigh.

1 Caching  Temporary storage of frequently accessed data (duplicating original data stored somewhere else)  Reduces access time/latency for clients 

Content Distribution March 8, : Application Layer1.

Active Network Applications Tom Anderson University of Washington.

CSE 534 – Fundamentals of Computer Networks Lecture 11: Content Delivery Networks (Over 1 billion served … each day) Based on slides by D. NEU.

1 Proceeding the Second Exercises on Computer and Systems Engineering Professor OKAMURA Laboratory. Othman Othman M.M.

Redirection and Load Balancing

SMUCSE 4344 application layer. SMUCSE 4344 application vs. application-layer protocols application-layer protocol is just one piece –how the end hosts.

Oasis: Anycast for Any Service Michael J. Freedman Karthik Lakshminarayanan David Mazières in NSDI 2006 Presented by: Sailesh Kumar.

Ao-Jan Su, David R. Choffnes, Fabián E. Bustamante and Aleksandar Kuzmanovic Department of EECS Northwestern University Relative Network Positioning via.

DNS: Domain Name System

Application-Layer Anycasting By Samarat Bhattacharjee et al. Presented by Matt Miller September 30, 2002.

Othman Othman M.M., Koji Okamura Kyushu University 1.

CPSC 441: Multimedia Networking1 Outline r Scalable Streaming Techniques r Content Distribution Networks.

2: Application Layer1 Chapter 2 outline r 2.1 Principles of app layer protocols r 2.2 Web and HTTP r 2.3 FTP r 2.4 Electronic Mail r 2.5 DNS r 2.6 Socket.

Application of Content Computing in Honeyfarm Introduction Overview of CDN (content delivery network) Overview of honeypot and honeyfarm New redirection.

Othman Othman M.M., Koji Okamura Kyushu University 1.

Kiew-Hong Chua a.k.a Francis Computer Network Presentation 12/5/00.

Multimedia and Networks. Protocols (rules) Rules governing the exchange of data over networks Conceptually organized into stacked layers – Application-oriented.

Flashback: A Peer-to-Peer Web Server for Flash Crowds Presented by Tom Batkiewicz CS 587x Fall ‘07.

1 Distributed Systems Distributed Web-Based Systems Chapter 12.

Drafting Behind Akamai (Travelocity-Based Detouring) Dr. Yingwu Zhu.

Globally Distributed Content Delivery Presenter: Baoning Wu 03/25/2003.

Content Distribution Network, Proxy CDN: Distributed Environment

CS 6401 Overlay Networks Outline Overlay networks overview Routing overlays Resilient Overlay Networks Content Distribution Networks.

Content Delivery Networks: Status and Trends Speaker: Shao-Fen Chou Advisor: Dr. Ho-Ting Wu 5/8/

1. Internet hosts:  IP address (32 bit) - used for addressing datagrams  “name”, e.g., ww.yahoo.com - used by humans DNS: provides translation between.

Content Distribution Networks (CDNs)

CSEN 404 Application Layer II Amr El Mougy Lamia Al Badrawy.

John S. Otto Mario A. Sánchez John P. Rula Fabián E. Bustamante Northwestern, EECS.

Multicast in Information-Centric Networking March 2012.

Content Distribution Networks

Presentation on Distributed Web Based Systems Submitted by WWW

Content Distribution Networks

Proxy Caching for Streaming Media

Caching Temporary storage of frequently accessed data (duplicating original data stored somewhere else) Reduces access time/latency for clients Reduces.

Ad-blocker circumvention System

Internet Applications

ECE 671 – Lecture 16 Content Distribution Networks

Edge computing (1) Content Distribution Networks

Content Distribution Networks

EE 122: Lecture 22 (Overlay Networks)

AKAMAI Content Delivery Services

Presentation transcript:

{ Content Distribution Networks ECE544 Dhananjay Makwana Principal Software Engineer, Semandex Networks 5/2/14ECE544

Credits Paul Krzyzanowski, Rutgers University Vyas Sekar, Stony Brook University Peter Steenkiste, CMU 5/2/14ECE544

 1. Motivation / Problem  2. Evolution  3. Implementation  4. Mapping users to CDN servers  5. Types of Content  6. Hybrid Approaches  7. Further Reading  8. Q&A Overview 5/2/14ECE544

 Quality/Performance expectations are rising  Serving Content from a single location  Scalability  Reliability  Performance  “Flash Crowd” problem Motivation / Problem 5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

 Edge Caches: work with ISP and networks everywhere to install edge caches  Edge = close to customers  Content delivery: getting content to the edge caches  Content can be objects, video, or entire web sites  Mapping: find the “closest” edge server for each user and deliver content from that server  Network proximity not the same as geographic proximity  Focus is on performance as observed by user (quality) CDN to the rescue 5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

 How to map clients to servers?  What metrics? Latency, Load  DNS, HTTP 304 response, anycast, etc.  How/where to replicate content?  On demand?  Proactive/prefetch?  everywhere or close to demands? Questions 5/2/14ECE544

 Application based  Routing based  DNS based Mapping 5/2/14ECE544

 HTTP supports simple way to indicate that Web page has moved (30X responses)  Server receives Get request from client  Decides which server is best suited for particular client and object  Returns HTTP redirect to that server  Pros  Can make informed application specific decision  Cons  May introduce additional overhead  Multiple connection setup, name lookups, etc.  Could interact poorly with some browser implementations Application Based 5/2/14ECE544

 IP Anycast  Use BGP to announce same destination IP from multiple places.  Clients are agnostic and connect to Anycast address  ISP router routes to “nearest” anycast server.  Pros  All IP infrastructure is available  Potential scaling to internet level  Cons  Cannot incorporate application policy  Stateful connections may create problems  Relatively less dynamic Routing Based 5/2/14ECE544

 DNS  Clients perform typical DNS query.  DNS servers are locality aware  Reply with “best” server available  Pros  Existing DNS protocol (fully supported)  Fully flexible application/content provider policies  Potential other uses (e.g. Ad serving, Video transcoding)  Cons  Multiple DNS queries  Depends upon an efficient implementation DNS Based 5/2/14ECE544

 Example Akamai  Akamai does this via Dynamic DNS  Customer modifies URLs (akamizes)  Direct requests to right content servers  Resolve a host name based on:  Service requested (e.g. QuickTime, Windows Media, HTML)  Content requested (css, js, swf, jpeg etc.)  Server health  Server load  User location  Network status  Load balancing Mapping (DNS Based) 5/2/14ECE544

5/2/14ECE544

5/2/14ECE544

 Resolve a7.g.akamai.net  NS resolver contacts root server  Root server sends a referral to a name server responsible for.net  Resolver queries.net name server  Returns a referral for.akamai.net  This is the top-level Akamai server  Resolver queries a top-level Akamai server  Returns a referral for.g.akamai.net  Low-level Akamai server (TTL approx 1 hour)  Low-level servers are in the same location as edge servers closest to user  Resolver queries a low-level Akamai server  Returns IP addresses of servers available to satisfy the request  Short TTL (several seconds to 1 minute) DNS Resolution 5/2/14ECE544

5/2/14ECE544

 Static content  Cached depending on original site's requirements (never to forever)  Dynamic content  Caching proxies cannot do this  Akamai uses Edge Side Includes technology (  Assembles dynamic content on edge servers  Similar to server-side includes  Page is broken into fragments with independent caching properties  Assembled on demand  Streaming media  Live stream is sent to an entry-point server in the Akamai network  Stream is delivered from the entry-point server to multiple edge servers  Edge servers serve content to end users. Content Types 5/2/14ECE544

 The Akamai Network: A Platform for High- Performance Internet Applications  Erik Nygren, Ramesh Sitaraman & Jennifer Sun  Improving performance on the Internet  Tom Leighton  Globally Distributed Content Delivery  John Dilley et. al Further Reading 5/2/14ECE544

Questions? 5/2/14ECE544 Thank You !