• Save
AWS Cloud Kata 2013 | Singapore - Opening Keynote: Running Lean & Scaling Fast - Dr Werner Vogels
Upcoming SlideShare
Loading in...5
×
 

AWS Cloud Kata 2013 | Singapore - Opening Keynote: Running Lean & Scaling Fast - Dr Werner Vogels

on

  • 692 views

 

Statistics

Views

Total Views
692
Views on SlideShare
692
Embed Views
0

Actions

Likes
2
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

AWS Cloud Kata 2013 | Singapore - Opening Keynote: Running Lean & Scaling Fast - Dr Werner Vogels AWS Cloud Kata 2013 | Singapore - Opening Keynote: Running Lean & Scaling Fast - Dr Werner Vogels Presentation Transcript

  • 21st Century Application Architectures Dr. Werner Vogels CTO, Amazon.com
  • @werner #21century
  • Fast GrowthSlow but steady Predictable peaksVariable peaks How will your startup be? View slide
  • Where will your users be? View slide
  • 503 Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
  • 503 Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
  • In 2007 …
  • The Old World All resources are constrained Capital Capacity Geography Physics People Scope
  • Typical Weekly Traffic to Amazon.com Sunday Monday Tuesday Friday SaturdayWednesday Thursday
  • Capacity Held Sunday Monday Tuesday Friday SaturdayWednesday Thursday Amazon.com Capacity Before EC2 Capacity Used
  • 39% 61% Amazon.com Capacity Before Capacity Held Capacity Used Sunday Monday Tuesday Friday SaturdayWednesday Thursday
  • November Traffic to Amazon.com Black Friday Cyber Monday Capacity Held November 1st
  • Capacity Held November Traffic to Amazon.com November 1st
  • 76 % 24 November Traffic to Amazon.com Capacity Held Capacity Used
  • November 10, 2010 October 31, 2011
  • Sunday Monday Tuesday Friday SaturdayWednesday Thursday Did We Solve the Problem? Capacity Held Capacity Used
  • Yes!Capacity Held Capacity Used Sunday Monday Tuesday Friday SaturdayWednesday Thursday
  • The New World Unconstrained (except for physics)
  • On and Off Fast Growth Variable peaks Predictable peaks Elastic capacity
  • On and Off Fast Growth Predictable peaksVariable peaks WASTE CUSTOMER DISSATISFACTION Elastic capacity
  • Elastic cloud capacity Traditional IT capacity Your IT needs Time Capacity Elastic capacity
  • Fast GrowthOn and Off Predictable peaksVariable peaks Elastic capacity
  • From one instance…
  • …to thousands
  • …back to one
  • 21st Century Architectures Build systems the way you always wanted to, but never could Secure High performance Fault Tolerant Scalable Cost-effective
  • Everything is a programmable resource Data centers Networks Compute Storage Databases Load Balancers
  • Resource focus Business focus Fixed & rigid Long change cycles Top down control Evolving & adapting Rapid change cycles Decentralized & emergent
  • The failure of resource focused projects 31% of projects never complete 52% of completed projects overrun the budget
  • Inaccurate resource estimates Changing requirements Unmanaged risks & assumptions Increasing complexity Why do they fail?
  • Observations
  • Massive Mismatches It is Out of Control Enterprise Internet Project Cycles Years Hours Project Life Spans Decades Months Project Frequencies 101 - 102 106 Investment Decision Cycles Mythical Person-Months Impulse Implementation Scale Enterprise Global Decision Process Orderly Centralized Chaotic Individualized
  • The Commandments of 21st Century Architectures
  • Thou shalt use new concepts to build new applications
  • 21st Century Architectures are
  • Decompose into small, loosely coupled, stateless building blocks
  • IMDB widget architecture Amazon Web Server Render Process Service Call IMDB Service IMDB Database Customer
  • Before Customer Amazon Web Server Generic S3 HTML Puller S3 HTML Store After Amazon Web Server Render Process Service Call IMDB Service IMDB Database Customer
  • Automate your application and processes
  • Let business levers control the system
  • Architect with cost in mind
  • 21st Century Architectures are
  • Protecting your customer is the first priority
  • In production deploy to at least two availability zones
  • Integrate security into your application from ground up
  • Treat your architecture as a continuous evolving, living concept
  • Build, test, integrate and deploy continuously
  • seconds mean time between deployments (weekday) Max number of deployments in a single hour Mean number of hosts simultaneously receiving a deployment Max number of hosts simultaneously receiving a deployment 11.6 1,079 10,000 30,000 Deployments at Amazon.com
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 WWW1 WWW2 WWW3 WWWn Availability Zone 2 WWW1 WWW2 WWW3 WWWn Availability Zone 3
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 WWW1 WWW2 WWW3 WWWn Availability Zone 2 WWW1 WWW2 WWW3 WWWn Availability Zone 3
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 WWW1 WWW2 WWW3 WWWn Availability Zone 2 WWW1 WWW2 WWW3 WWWn Availability Zone 3
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 WWW1 WWW2 WWW3 WWWn Availability Zone 2 WWW1 WWW2 WWW3 WWWn Availability Zone 3
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 WWW1 WWW2 WWW3 WWWn Availability Zone 2 WWW1 WWW2 WWW3 WWWn Availability Zone 3
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 WWW1 WWW2 WWW3 WWWn Availability Zone 2 WWW1 WWW2 WWW3 WWWn Availability Zone 3
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 Availability Zone 2 Availability Zone 3 WWW2 WWWnWWW3WWW1 WWW2 WWWnWWW3WWW1 WWW1 WWW2 WWW3 WWWn Availability Zone 1 Availability Zone 2 Availability Zone 3 WWW2 WWWnWWW3WWW1 WWW2 WWWnWWW3WWW1
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 Availability Zone 2 Availability Zone 3 WWW2 WWWnWWW3WWW1 WWW2 WWWnWWW3WWW1 WWW1 WWW2 WWW3 WWWn Availability Zone 1 Availability Zone 2 Availability Zone 3 WWW2 WWWnWWW3WWW1 WWW2 WWWnWWW3WWW1
  • Load Balancer WWW1 WWW2 WWW3 WWWn Availability Zone 1 Availability Zone 2 Availability Zone 3 WWW2 WWWnWWW3WWW1 WWW2 WWWnWWW3WWW1 WWW1 WWW2 WWW3 WWWn Availability Zone 1 Availability Zone 2 Availability Zone 3 WWW2 WWWnWWW3WWW1 WWW2 WWWnWWW3WWW1
  • Don’t think in single failures
  • Don’t treat failure as an exception
  • 21st Century Architectures are
  • Entia non sunt multiplicanda Praeter necessitiatem
  • Assume nothing
  • Use late binding
  • Change your mind, frequently, when needed
  • Don’t be afraid to make mistakes
  • 21st Century Architectures are
  • Instrument everything, all the time
  • Inspect the whole distribution
  • Put everything in logs
  • The Commandments of 21st Century Architectures
  • Controllable Architect with cost in mind Adaptive Make no assumtpions Resilient Don’t treat failure as an exception Data-driven Put everything in logs
  • Everything is a programmable resource
  • Thou shalt turn off the lights
  • Thank you werner@amazon.com Q&A at the AWS Booth