slides.0426.2011.b - ACMS:TheAkamai Configuration...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Alex Sherman (Akamai Technologies, Columbia University)  Phil Lisiecki (Akamai Technologies) Andy Berkheimer (Akamai Technologies)   Joel Wein (Akamai Technologies, Polytechnic University) ACMS: The Akamai  Configuration  Management System Author’s slides edited by Brian Cho
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ACMS The Akamai Platform Akamai operates a Content Delivery Network of  15,000+ servers distributed across 1,200+ ISPs in 60+  countries Web properties (Akamai’s customers) use these  servers to bring their web content and applications  closer to the end-users
Background image of page 2
ACMS Problem: configuration and control Even with the widely distributed platform customers  need to maintain the control of how their content is  served Customers need to configure their service options with  the same ease and flexibility as if it was a centralized,  locally hosted system 
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ACMS Problem (cont)  Customer profiles include hundreds of  parameters. For example:  Cache TTLs Allow lists Whether cookies are accepted Whether application sessions are stored  In addition, internal Akamai services require  dynamic reconfigurations (mapping, load- balancing, provisioning services)
Background image of page 4
ACMS Why is this difficult?  15,000 servers must synchronize to the latest  configurations within a few minutes  Some servers may be down or “partitioned-off” at  the time of reconfiguration A server that comes up after some downtime must  re-synchronize quickly Configuration may be initiated from anywhere on  the network and must reach all other servers Discussion: Many more locations (1,200+ ISPs in 60+  countries) than e.g. MapReduce, GFS Discussion: Why is this easy?
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ACMS Outline High-level overview of the functioning configuration  system Distributed protocols that guarantee fault-tolerance  (based on earlier literature) Operational experience and evaluation
Background image of page 6
ACMS Assumptions Configuration files may vary in size from a few  hundred bytes to 100MB Submissions may originate from anywhere on  the Internet  Configuration files are submitted in their  entirety (no diffs) 
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ACMS System Requirements High availability  – system must be up 24x7 and accessible  from various points on the network  Fault-tolerant storage  of configuration files for  asynchronous delivery  Efficient delivery  – configuration files must be delivered to  the “live” edge servers quickly Recovery  – edge servers must “recover” quickly Consistency
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 12/08/2011 for the course CS 525 taught by Professor Gupta during the Spring '08 term at University of Illinois, Urbana Champaign.

Page1 / 31

slides.0426.2011.b - ACMS:TheAkamai Configuration...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online