Content Delivery: Extending to the Edge through the IX

Slides:



Advertisements
Similar presentations
Amazon CloudFront An introductory discussion. What is Amazon CloudFront? 5/31/20122© e-Zest Solutions Ltd. Amazon CloudFront is a web service for content.
Advertisements

Akamai networks,48000 servers and 70 countries in the world.
19 Historical overview Main challenge: How to distribute content in high quality over the Internet cost-effectively? • Traditional “Best-effort” model:
Business Continuity and DR, A Practical Implementation Mich Talebzadeh, Consultant, Deutsche Bank
Web Caching Schemes1 A Survey of Web Caching Schemes for the Internet Jia Wang.
Cis e-commerce -- lecture #6: Content Distribution Networks and P2P (based on notes from Dr Peter McBurney © )
Web Caching and CDNs March 3, Content Distribution Motivation –Network path from server to client is slow/congested –Web server is overloaded Web.
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.
Peering, network sharing, interconnects Eckart Zollner September 2014.
{ Content Distribution Networks ECE544 Dhananjay Makwana Principal Software Engineer, Semandex Networks 5/2/14ECE544.
Kiew-Hong Chua a.k.a Francis Computer Network Presentation 12/5/00.
Adaptive Web Caching CS411 Dynamic Web-Based Systems Flying Pig Fei Teng/Long Zhao/Pallavi Shinde Computer Science Department.
Proxy Servers.
Flashback: A Peer-to-Peer Web Server for Flash Crowds Presented by Tom Batkiewicz CS 587x Fall ‘07.
Windows Azure. Azure Application platform for the public cloud. Windows Azure is an operating system You can: – build a web application that runs.
Content Delivery Networks: Status and Trends Speaker: Shao-Fen Chou Advisor: Dr. Ho-Ting Wu 5/8/
Routing Algorithms Lecture Static/ Dynamic, Direct/ Indirect, Shortest Path Routing, Flooding, Distance Vector Routing, Link State Routing, Hierarchical.
Web Werks Data Center Connects To All Regional ISPs in India to Improve Network Latency.
WHAT'S THE DIFFERENCE BETWEEN A WEB APPLICATION STREAMING NETWORK AND A CDN? INSTART LOGIC.
MICROSOFT AJAX CDN (CONTENT DELIVERY NETWORK) Make Your ASP.NET site faster to retrieve.
COMPUTER NETWORKS Quizzes 5% First practical exam 5% Final practical exam 10% LANGUAGE.
Content Delivery Cloud A Better Alternative To Your Content Delivery Network (CDN) ©2013 Riverbed Technology Confidential and Proprietary.
INTRODUCTION TO WEB HOSTING
Instructor Materials Chapter 1: LAN Design
Data Virtualization Demoette… Packaged Query Single Select Option
Peering at the Internet’s Frontier: A First Look at ISP Interconnectivity in Africa Arpit Gupta, Matt Calder, Nick Feamster, Marshini Chetty, Enrico.
DDoS In the Real World Do DDoS attacks really happen?
DocFusion 365 Intelligent Template Designer and Document Generation Engine on Azure Enables Your Team to Increase Productivity MICROSOFT AZURE APP BUILDER.
Technologies and Applications
Content Distribution Networks
Vidcoding Introduces Scalable Video and TV Encoding in the Cloud at an Affordable Price by Utilizing the Processing Power of Azure Batch MICROSOFT AZURE.
Principles of Network Applications
What is Fibre Channel? What is Fibre Channel? Introduction
DDoS In the Real World Do DDoS attacks really happen?
Living in a Network Centric World
Living in a Network Centric World
Web Caching? Web Caching:.
A Modern Intranet Integration that Extends the Value of Your Microsoft Office 365 Deployment, Boosts Productivity, and Enhances Collaboration OFFICE 365.
Physical Architecture Layer Design
Utilization of Azure CDN for the large file distribution
Cloud Computing.
Internet Networking recitation #12
AWS. Introduction AWS launched in 2006 from the internal infrastructure that Amazon.com built to handle its online retail operations. AWS was one of the.
How do we decide where to deploy to next?
Chapter 16: Distributed System Structures
Why do we need cloud network services? Let’s dig into the content and explore the answer.
ECE 671 – Lecture 16 Content Distribution Networks
Chapter 7: Consistency & Replication IV - REPLICATION MANAGEMENT -Sumanth Kandagatla Instructor: Prof. Yanqing Zhang Advanced Operating Systems (CSC 8320)
Distributed Content in the Network: A Backbone View
Internet Interconnection
Overlay Networking Overview.
Connected Building SERVICES
Distributed Systems CS
Dell Data Protection | Rapid Recovery: Simple, Quick, Configurable, and Affordable Cloud-Based Backup, Retention, and Archiving Powered by Microsoft Azure.
Living in a Network Centric World
Fulfilling omni-channel demand Introduction
AWS Cloud Computing Masaki.
Living in a Network Centric World
It Followed Me Home: Exploring Strong Last Hop Devices and CDNs
Living in a Network Centric World
Living in a Network Centric World
Living in a Network Centric World
Jan Chrillesen, Stofa A/S
Building global and highly-available services using Windows Azure
Living in a Network Centric World
EE 122: Lecture 22 (Overlay Networks)
Living in a Network Centric World
Report from the trenches of an HTML5 game provider
SwiNOG May 2013 Ian Cleary – Director Internet Services EMEA
Living in a Network Centric World
Presentation transcript:

Content Delivery: Extending to the Edge through the IX March 2018 | Ivan Sanz Introduction: Ivan Sanz Infrastructure Acquisition Manager for Fastly. Fastly is a content delivery network based in the US and we have physical presence in nearly 50 POPs across 6 continents. I’m responsible for Fastly’s expansion strategy in newer markets - this includes South America, Africa, India and the Middle East. Before I get started, I want to take a quick poll of the audience: How many of you are familiar with what a CDN is ? How many of you use a CDN for your operations?

Agenda What’s a CDN? Pursuit of the Edge How IXs Extend the Edge The Fastly Network I’ll introduce CDN Characteristics Functionality Compare sites with / without CDNs Next, I’ll explain why CDNs are pushing to get closer to end Users Elaborate on the role latency plays in this I will also discuss how pursuing the edge is challenging and presents its own problems Then, I’ll talk about how IXs enable better connectivity at the edge. Last, I’ll finish with the Fastly approach to edge delivery and how we are building a better Internet.

What’s a CDN? So, first, What’s a CDN?

Content Delivery Network Network of caching servers Geographically dispersed; each location a POP Intermediary between Users and Origin Users are served from closest edge server Network of “edge” servers that hold temporary copies of content (think videos, songs, HTML, any type of file your browser or application might request from a host) Installed in data centers all around the world Act as intermediary (all requests go to them first) If content is on an edge server, content is served from closest machine So, we now some of the defining characteristics, but how does this look in practice? Let’s start with a site that does not have a CDN Part 1 – What’s a CDN?

A site without a CDN... ...is slow This request takes at minimum 200ms before content flows Request São Paulo Concepción Content Part 1 – What’s a CDN?

A site without a CDN... ...is not redundant If Origin is unavailable, User receives an error Request São Paulo Concepción 503 Error User in Concepcion requests content. Hits edge node in Santiago first. If content is there, content is returned quickly. If not, edge node in Santiago fetches content from origin in Sao Paulo over preexisting connection Subsequent users will receive the file from cache in Santiago and no additional requests to the origin will be made. Multiple by thousands and you’ll still be fine. Your origin will only see one request. Part 1 – What’s a CDN?

A site without a CDN... ...is not scalable 100,000 Request São Paulo Here you might have a slight demand in traffic but the origin is fine. Now, a DDoS attack comes and multiplies your requests by 100K, killing your origin. Part 1 – What’s a CDN?

A site with a CDN... ...is fast Instead of São Paulo, request goes to Santiago. Content flows in less than 10ms São Paulo Santiago Concepción Buenos Aires User in Concepcion requests content. Hits edge node in Santiago first. If content is there, content is returned quickly. If not, edge node in Santiago fetches content from origin in Sao Paulo over preexisting connection Subsequent users will receive the file from cache in Santiago and no additional requests to the origin will be made. Multiple by thousands and you’ll still be fine. Your origin will only see one request. Part 1 – What’s a CDN?

A site with a CDN... ...is fast If content is not in cache (cache-miss), existing keep-alive connections enable fast origin pull São Paulo Santiago Concepción Buenos Aires If not, edge node in Santiago fetches content from origin in Sao Paulo over preexisting connection Subsequent users will receive the file from cache in Santiago and no additional requests to the origin will be made. Part 1 – What’s a CDN?

A site with a CDN... ...is redundant If Santiago is unavailable, User is routed to another site São Paulo Santiago Concepción Buenos Aires User will be served from Sao Paulo or Buenos Aires - before origin Part 1 – What’s a CDN?

A site with a CDN... ...is scalable Edge nodes absorb traffic and keep your services and origin running São Paulo Santiago Buenos Aires Part 1 – What’s a CDN?

Why Use a CDN? Fast Content moves closer to end users. Reduces latency. Redundant If a POP is offline, others serve traffic. If Origin is offline, CDN continues serving from cache. Scalable: Entire network can absorb traffic spikes and DDoS attacks. To summarize, these are some of the reasons to use a CDN. Fast - Redundant Scalable However, if all of these features are inherent in a distributed systems model? How do CDNs differentiate themselves? Part 1 – What’s a CDN?

Pursuit of the Edge: Getting Closer to End Users One big way is by getting closer to end users!

Why Get Closer to Users? Although redundancy and scalability are important… being Fast is one of the most impactful and measurable aspects of User experience In fact, studies time and time again show that users will abandon a website or application if load time is too long. So, CDNs push to get closer to Users to improve user experience even more. The power to say “I am faster than that provider” Part 2 – Pursuit of the Edge

CDN Response Times for Dynamic Delivery (Chile) <<CDNs use this as a differentiator and start to compete on speed - Cedexis ratings>> I’m serious - We’re all competing on it whether we like it or not. In fact, Cedexis is a metrics company that measures CDNs and many other types of providers. Look - Fastly is fastest for Dynamic Delivery in Chile! https://www.cedexis.com/get-the-data/country-report/ 13 March 2018, Country: Chile Part 2 – Pursuit of the Edge

So We Should Build More POPs? It really depends. The key to a great user experience is more complex than simply building a POP closer to end users to reduce latency... Part 2 – Pursuit of the Edge

It Is A Complex Trade Off Expanding a network introduces new infrastructure risks... Power required for dense POPs is hard to find outside of big cities Data centers of high security and reliability are limited Connectivity for communication with origin may be less reliable All of these jeopardize a CDN’s ability to run a network with the high standard of service and quality you would expect. Part 2 – Pursuit of the Edge

It Is A Complex Trade Off And expanding the server pool introduces software risks... Cache-Hit Ratio will decrease and traffic to origin will increase Purging old content becomes more challenging because more servers must successfully evict content As you continue to distribute load across a higher denominator, cache hit ratio will necessarily fall. Purging gets more difficult as you increase the pool of servers that need to be notified of new content So, I just said that everyone is reaching for the edge, but Part 2 – Pursuit of the Edge

It Is A Complex Trade Off So everyone is reaching for the edge but doing so is difficult and can present its own risks to the User experience... As you continue to distribute load across a higher denominator, cache hit ratio will necessarily fall. Purging gets more difficult as you increase the pool of servers that need to be notified of new content So, I just said that everyone is reaching for the edge, but Part 2 – Pursuit of the Edge

So Who Is Going to Save Us? Nuestros amigos de PITChile Part 2 – Pursuit of the Edge

How IXs Extend the Edge

IXs Bring Networks Together Internet Exchanges provide a shared fabric and a direct path for bits to move from one network to another. Part 3 – How IXs Extend the Edge

IXs Improve Operations Internet Exchanges improve routing and latency, and reduce costs for network operators in a region. Part 3 – How IXs Extend the Edge

Traffic Flow Without an IX ISP 1 ISP 3 ISP 4 ISP 2 TRANSIT In this example, without an IX, ISPs with users accessing Fastly content might have to hop across multiple networks before connecting to content served by the Fastly CDN - might even leave the country - depending on routing Congestion on a neighboring network Paying transit to carry bits Part 3 – How IXs Extend the Edge

Traffic Flow With an IX ISP 1 ISP 3 PITChile ISP 2 ISP 4 In the CDN example, because of PITChile any ISP connected to PITChile has a direct path to all content delivered by Fastly. Either using the route server or bilateral sessions, traffic should move seamlessly to / from Fastly across this infrastructure Part 3 – How IXs Extend the Edge

With PITChile, we are BGP neighbors and less than ~10ms apart - even if we are physically far from one another ISP 2 Arica PITChile ISP 1 Santiago Concepción Part 3 – How IXs Extend the Edge

Provides reliable connectivity to CDN POP in metro market without infrastructure and software risks ISP 2 Arica PITChile ISP 1 Santiago In other words, IX provide reliable connectivity to a CDN POP in major metro market with the CDN Concepción Part 3 – How IXs Extend the Edge

The Best of Both Worlds Very reliable access to powerful CDN POPs in major metro markets, with very limited additional latency for regional Users Part 3 – How IXs Extend the Edge

The Fastly Network

Real-Time with Real Control At Fastly we... build very powerful, cache-dense POPs enable our Customers to control delivery provide real-time analytics … and much more... Part 3 – How IXs Extend the Edge

Santiago Now Live!

Summary

Summary Use a CDN to improve speed, redundancy and scalability Part 3 – How IXs Extend the Edge

Summary CDNs can efficiently localize content from anywhere in the world to a major metro region Part 3 – How IXs Extend the Edge

Summary CDNs could extend out to the edge to further localize content but this comes with limitations and risks to User experience Part 3 – How IXs Extend the Edge

Summary IXs unlock wider access to content by providing reliable, cost-effective paths for edge Users to connect to powerful CDN POPs Part 3 – How IXs Extend the Edge

Summary Fastly is now on the PITChile Santiago exchange. We would love to make the Internet faster for everyone. Peer with us! Part 3 – How IXs Extend the Edge

Thank you. ivan@fastly.com