Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Akamai company profile

1,060 views

Published on

Company profile of a leading hosting company

Published in: Technology
  • Be the first to comment

Akamai company profile

  1. 1. Akamai CDN and Peering Bob Lau Akamai Technologies PH OpenIX 27June2014
  2. 2. Agenda Akamai Introduction •Who’s Akamai? • Intelligent Platform & Traffic Snapshot ©2012 AKAMAI | FASTER FORWARDTM Basic Technology • Akamai mapping • Finding the IP address •www.example.com Peering with Akamai •Why Akamai peer with ISPs •Why ISPs peer with Akamai
  3. 3. Akamai Introduction
  4. 4. ©2012 AKAMAI | FASTER FORWARDTM Akamai Overview Who is Akamai? Akamai is a leading provider of a Cloud platform, which delivers, accelerates and secure content and APPLICATIONS over the Internet. Our key differentiator is our highly distributed (intelligent) platform, made up of more than 150,000 servers in 92 countries. •Public company – symbol NASDAQ: AKAM •Founded: 1998 •Headquarters: Cambridge, MA, USA •30+ worldwide offices, including Europe and Asia •4,300+ employees worldwide
  5. 5. The Akamai Intelligent Platform The world’s largest on-demand, distributed computing platform delivers all forms of web content and applications The Akamai Intelligent Platform: 150,000+ Servers Typical daily traffic: • More than 2 trillion requests served • Delivering over 21 Terabits/second • 15-30% of all daily web traffic 2,000+ Locations ©2012 AKAMAI | FASTER FORWARDTM 92 Countries 1,200+ Networks 700+ Cities
  6. 6. Basic Technology Akamai mapping
  7. 7. ©2012 AKAMAI | FASTER FORWARDTM How CDNs Work When content is requested from CDNs, the user is directed to the optimal server •This is usually done through the DNS, especially for non-network CDNs, e.g. Akamai • It can be done through anycasting for network owned CDNs Users who query DNS-based CDNs be returned different A (and AAAA) records for the same hostname This is called “mapping” The better the mapping, the better the CDN
  8. 8. How Akamai CDN Work Example of Akamai mapping • Notice the different A records for different locations: [NYC]% host www.symantec.com www.symantec.com CNAME e5211.b.akamaiedge.net. e5211.b.akamaiedge.net. A 207.40.194.46 e5211.b.akamaiedge.net. A 207.40.194.49 [Boston]% host www.symantec.com www.symantec.com CNAME e5211.b.akamaiedge.net. e5211.b.akamaiedge.net. A 81.23.243.152 e5211.b.akamaiedge.net. A 81.23.243.145 ©2012 AKAMAI | FASTER FORWARDTM
  9. 9. How Akamai CDN Work Akamai use multiple criteria to choose the optimal server •These include standard network metrics: ©2012 AKAMAI | FASTER FORWARDTM •Latency •Throughput •Packet loss •These also include things like CPU load on the server, HD space, network utilization, etc.
  10. 10. Finding the IP Address: The Akamai Way ©2012 AKAMAI | FASTER FORWARDTM a212.g.akamai.net End User Akamai High-Level DNS Servers 4 example.com 10 g.akamai.net 1 Browser’s Cache OS 2 Local Name Server 3 example.com’s nameserver 6 7 www.example.com 9 15.15.125.6 16 15 20.20.123.55 11 Akamai Low-Level DNS Servers 12 a212.g.akamai.net 30.30.123.5 13 14 .net Root 510.10.123.5 (InterNIC) akamai.net 8
  11. 11. 1. Enduser types www.retailer.com into browser 2. Browser retrieves entire site from Akamai cache at the edge 3. HTML instructs browser to get objects from Akamai 4. Browser retrieves images from optimal Akamai EdgeServer HTML Whole Site Delivery (for Static Sites) ©2012 AKAMAI | FASTER FORWARDTM Origin Infrastructure End User
  12. 12. 1. Enduser types www.retailer.com into browser 2. Browser requests HTML from optimal Akamai EdgeServer 3. Akamai EdgeServer retrieves HTML from origin infrastructure 4. Akamai EdgeServer sends HTML to browser 5. Browser retrieves images from optimal Akamai EdgeServer HTML Whole Site Delivery (for Dynamic Sites) ©2012 AKAMAI | FASTER FORWARDTM Origin Infrastructure HTML End User
  13. 13. With Akamai: “Just-in-time caching” of dynamic and “cold” content by Akamai Pre-fetching 1) Enduser types www.retailer.com into browser 2) Browser requests HTML from optimal Akamai EdgeServer 3) Akamai EdgeServer “GETs” HTML from origin infrastructure 4) Akamai EdgeServer parses HTML and requests uncached images from origin while delivering HTML to browser 5) EdgeServer delivers “Akamaized” images to browser ©2012 AKAMAI | FASTER FORWARDTM Origin Infrastructure End User HTML
  14. 14. Why CDNs Peer with ISPs The first and foremost reason to peer is improved performance • Since a CDN tries to serve content as “close” to the end user as possible, peering directly with networks (over non-congested links) obviously helps Peering gives better throughput • Removing intermediate AS hops seems to give higher peak traffic for same demand profile •Might be due to lower latency opening TCP windows faster •Might be due to lower packet loss ©2012 AKAMAI | FASTER FORWARDTM
  15. 15. Why CDNs Peer with ISPs Redundancy •Having more possible vectors to deliver content increases reliability Burstability •During large events, having direct connectivity to multiple networks allows for higher burstability than a single connection to a transit provider Burstability is important to CDNs •One of the reasons customers use CDNs is for burstability ©2012 AKAMAI | FASTER FORWARDTM
  16. 16. Why CDNs Peer with ISPs Peering reduces costs • Reduces transit bill (duh) Network Intelligence • Receiving BGP directly from multiple ASes helps CDNs map the Internet Backup for on-net servers • If there are servers on-net, the IX can act as a backup during downtime and overflow • Allows serving different content types ©2012 AKAMAI | FASTER FORWARDTM
  17. 17. Why ISPs peer with CDNs Performance • CDNs and ISPs are in the same business, just on different sides - we both want to serve end users as quickly and reliably as possible • You know more about your network than any CDN ever will, so working with the CDN directly can help them deliver the content more quickly and reliably Cost Reduction • Transit savings • Possible backbone savings ©2012 AKAMAI | FASTER FORWARDTM
  18. 18. Conclusions Summary
  19. 19. Summary •Akamai Intelligent Platform •Highly distributed edge servers •Akamai mapping is different than BGP routing •Peering with Akamai •Improve user experience •Reduce transit/peering cost ©2012 AKAMAI | FASTER FORWARDTM
  20. 20. ©2012 AKAMAI | FASTER FORWARDTM Questions? Bob Lau <chlau@akamai.com> More information: Peering: http://as20940.peeringdb.com Akamai IO: http://www.akamai.com/html/io

×