1. Content Delivery Networks - Principles & Practice Northeastern& Akamai Technologies Ravi Sundaram

2. Outline CDNs - Review of mechanicsCDNs - Review of mechanics FirstPoint - Traffic Management for mirrored websitesFirstPoint - Traffic Management for mirrored websites

3. Internet Content Providers End Users The Web: Simple on the Outside…

4. NAP UUNet Qwest AOL Network Providers Content Providers End Users Peering Points …But Problematic on the Inside

5. Why does my click not work Latency - Browser takes a long time to load the pageLatency - Browser takes a long time to load the page Packet Loss - Browser hangs, user needs to hit refreshPacket Loss - Browser hangs, user needs to hit refresh Jitter - Streams are jerkyJitter - Streams are jerky Server load - Browser connects but does not fully load the pageServer load - Browser connects but does not fully load the page Broken/missing contentBroken/missing content

6. The Akamai Solution Servers at Network Edge Content Providers End Users NAP

7. 3 Content Provider’s Web Server DNS WWW.XYZ.COM 1 Downloading www.xyz.com - before CDNs User enters www.xyz.comUser enters www.xyz.com Browser requests IP address for www.xyz.comBrowser requests IP address for www.xyz.com Browser requests embedded objectsBrowser requests embedded objects Content provider’s web server returns HTMLContent provider’s web server returns HTML 10.10.123.8 2 Browser requests HTMLBrowser requests HTML DNS returns IP addressDNS returns IP address 4 7 6 Browser obtains IP addresses for hostnames listed in URLs of objects embedded on pageBrowser obtains IP addresses for hostnames listed in URLs of objects embedded on page Content provider’s web server returns embedded objectsContent provider’s web server returns embedded objects 10.10.123.8 5

8. DNS Resolution Browser’s Cache 1 OS 2 Local Name Server 3.com.net Root (InterNIC) 4 xyz.com DNS Servers 6 5 7 8 9 10 TTL: 1 Day TTL: 30 Minutes

9. Origin - Content Provider’s Web Server Delivery of Whole Site 6 6. Browser obtains content from optimal Akamai server WWW.XYZ.COM DNS 1. Browser requests DNS for IP of www.xyz.com 1 3 3. DNS returns IP of optimal Akamai server 5. Akamai server assembles page, contacting origin as needed 5 4. Browser requests Akamai server for content 4 2. DNS follows CNAME redirect to www.xyz.edgesuite.net 2

10. Delivery of Whole Site - DNS Redirect DNS CNAME RECORD www.xyz.com CNAME www.xyz.edgesuite.net 2D

11. Delivery of Whole Site - Page Assembly Site owners create container pages that can be populated with varying content Container Page [TTL=5d] [XYZ news, content, promotions, etc. TTL=5d] [Breaking headlines TTL=2h] [TTL=15m] [TTL=8h]

12. Benefits of CDNs Improved end-user experienceImproved end-user experience -reduce latency -reduce loss -reduce jitter Reduced network congestionReduced network congestion Increased scalabilityIncreased scalability Improved fault-toleranceImproved fault-tolerance Reduced vulnerabilityReduced vulnerability Reduced costsReduced costs

13. Outline CDNs - Review of mechanicsCDNs - Review of mechanics FirstPoint - Traffic Management for mirrored websitesFirstPoint - Traffic Management for mirrored websites

14. What is FirstPoint Traffic management system for mirrored websitesTraffic management system for mirrored websites Directs browser to the optimal mirrorDirects browser to the optimal mirror DNS basedDNS based Application level anycastApplication level anycast

15. Why FirstPoint Content providers have mirrored websitesContent providers have mirrored websites Content providers only want to offload embedded contentContent providers only want to offload embedded content -Control -Security -Performance

16. Mapping Problem How to improve user experience?

17. What is the Mapping Problem Problem of directing requests to servers so as to optimize end-user experienceProblem of directing requests to servers so as to optimize end-user experience -reduce latency -reduce loss -reduce jitter Assumption - servers are fine Assumption - servers are fine Applicable to 2 mirrors or 1500 Akamai locationsApplicable to 2 mirrors or 1500 Akamai locations

18. Attempt Measure which is closerMeasure which is closer -Closeness changes over time Measure frequentlyMeasure frequently -Bothers people -Too many to do ~500,000 unique nameservers on any given day 10 sec per measurement cycle

19. Idea TopologyTopology -relatively static -changes in BGP time -order of hours if not days CongestionCongestion -dynamic -changes in round-trip time -order of milliseconds

20. Topology Discovery - Proxy points Cluster X Y

21. Aliasing Router fabrics using HSRP (hot stand-by routing protocol)Router fabrics using HSRP (hot stand-by routing protocol) -correlate over time Routers with multiple interfacesRouters with multiple interfaces -source address of UDP/ICMP packets

22. Set cover Let sets represent proxy pointsLet sets represent proxy points Let elements represent nameserversLet elements represent nameservers Find minimum collection of proxy points covering nameserversFind minimum collection of proxy points covering nameservers X covers 1, 2, 3 and 4 X 1 234

23. Topology Discovery At each mirror maintain list of partial paths to nameserversAt each mirror maintain list of partial paths to nameservers At each epoch extend paths by 1, in randomized fashion, and exchange with other mirrorAt each epoch extend paths by 1, in randomized fashion, and exchange with other mirror If the two (partial) paths to a namerver have intersected then declare that nameserver done.If the two (partial) paths to a namerver have intersected then declare that nameserver done. If path has reached forbidden IP then waitIf path has reached forbidden IP then wait Use pair of proxies in case of failureUse pair of proxies in case of failure

24. Topology Discovery - Proxy points Data exchange

25. Topology Discovery 500,000 nameservers 500,000 nameservers reduced to 90,000 proxy points (clusters)

26. Histogram of cluster sizes

27. Congestion Measurement Problem - Still too many measurements to do. 90,000 measurements every 10s with 32B packets requires a few Mbps per mirror. Problem - Still too many measurements to do. 90,000 measurements every 10s with 32B packets requires a few Mbps per mirror. Solution - Importance based sampling Solution - Importance based sampling

28. CDF of End-user Load

29. Load Estimation 500,000 nameservers reduced to 90,000 clusters 90,000 clusters 7,000 account for 95% end-user load!

30. Mapping Problem - Solved! Maps built every 10s

31. FirstPoint Customers - how to tell?Customers - how to tell? -look for CNAME to akadns.net Customers - who?Customers - who? -High traffic content providers -Yahoo!, Microsoft, TicketMaster etc Price - don’t ask :)Price - don’t ask :) Competitors - whoCompetitors - who -one-of-a-kind service -boxes: Cisco, F5, Foundry

32. FirstPoint - other aspects Load-balancingLoad-balancing -estimate-based -feedback-based : https, snmp -cost-based: 95/5 Fast cutout in case of failoverFast cutout in case of failover Highly fault-tolerantHighly fault-tolerant -hardware duplication, leader election -overlay routing, BGP-based anycast Integration with other servicesIntegration with other services -DOS/Load failover

33. Microsoft

34. Related Work TopologyTopology -Spring, Mahajan, Wetherall, Sigcomm ‘02 -Govindan, Tangmunarunkit, Infocom ‘00 ClusteringClustering -Krishnamurthy, Wang, Sigcomm ‘00 -Bezstavros, Mehrotra, WWC ‘01 -Barford, Gast, Globecom 02 ClusteringClustering -Shaikh, Tewari, Agrawal, Infocom ‘00 -Krishnamurthy, Wills, Zhang, Sigcomm IMW ‘01

35. Patents (pending) Global load balancing across mirrored data centers. Utility # 20020129134Global load balancing across mirrored data centers. Utility # 20020129134 Method for predicting file download time from mirrored data centers in a global computer network. Utility # 20020124080Method for predicting file download time from mirrored data centers in a global computer network. Utility # 20020124080 Method for generating a network map. Utility # 20020078237Method for generating a network map. Utility # 20020078237 Method and system for protecting websites from public Internet threats. Filed 15 July 2002Method and system for protecting websites from public Internet threats. Filed 15 July 2002

36. Principles Open design principleOpen design principle -You need all the help you can get -Do not eliminate the obvious without trying first -Give serendipity a chance Scaling principleScaling principle -factor 10 difference means different domain -different domains need different techniques The common case principleThe common case principle -Zipf law is your friend -things cluster -optimize the common case

37. Conclusion The Internet will never be fast enough in all placesThe Internet will never be fast enough in all places People will want access to the Internet all the time and everywherePeople will want access to the Internet all the time and everywhere