Your SlideShare is downloading. ×
  • Like
  • Save
Enterprise Cloud Migration: A Perspective for CIOs - Simone Brunozzi
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Enterprise Cloud Migration: A Perspective for CIOs - Simone Brunozzi

  • 1,161 views
Published

 

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,161
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
4

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Enterprise  Cloud  Migra2on:     A  Perspec2ve  for  CIOs     Simone  Brunozzi   Technology  Evangelist,  APAC   Amazon  Web  Services  
  • 2. EnterpriseCloudMigrationA perspective for CIOsSimone BrunozziAWS Technology Evangelist, APACTwitter - @simon - Tag: #awstour
  • 3. NOT PART OF CORPORATE APPLICATIONS Amazon.com  Website   Supply  Chain  Management   Amazon.com’s Corporate ApplicationsAccounting, Tax,Planning Financial Systems Email & Calendar Laptops/Desktops & HR Systems Recruiting, training, payroll Telecom Knowledge Intranet, search,Source control, Developer Tools Management Tools Blogs, wiki, sharepointChange Mgmt, Issue tracking Employee Tools & Corporate Systems Payments   3rd  Party  Seller   Systems   Customer  Service  Center  So@ware   Technologies  
  • 4. What is the main goal of any Corporate IT?
  • 5. Cost of IT
  • 6. Corporate Applications KPICost of Corporate IT = Cost Per User # of Users
  • 7. Then, one day, you decide:Let’s migrate to the Cloud
  • 8. How the Cloud Reduces CostEconomies of scaleOn-demand capacityReduced operational costReserved Instances / Spot Instances
  • 9. Other BenefitsMuch greater than Cost Savings
  • 10. Colonel John “40 seconds” Boyd
  • 11. F-86 vs MIG-15
  • 12. F-86 vs MIG-15MIG-15 was better at climbing,turning, long distance visibilityHowever, F-86 had 90% wins
  • 13. Hydraulic flight stick
  • 14. F-86 real advantages- Better lateral visibility- Initiate maneuvers earlier(hydraulic flight stick, instead of manual)
  • 15. Why F-86 won often?F-86 couldn’t turn more quickly,but the pilot could initiate a turn morequickly
  • 16. Boyd’s OODA loop Act ObserveDecide Orient
  • 17. http://www.flickr.com/photos/jphilipson/2323690960/
  • 18. Speed ofExecution
  • 19. Old Infrastructure = Speed BumpsHardware must be carefully chosenProvisioning cycles are longEverything must be built from scratch(e.g. file store, DB, etc.)
  • 20. AWS Removes Speed BumpsSwitch between instance typesProvisioning is an API callPrebuilt components
  • 21. A BIG Undo button "
  • 22. Start Finish Ideal Project
  • 23. Start Finish Ideal Project Actual Project
  • 24. Thomas Edison
  • 25. Iteration, not Inspiration
  • 26. Case StudyDeployment at Amazon
  • 27. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn
  • 28. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn
  • 29. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn = new version
  • 30. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn = new version
  • 31. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn = new version
  • 32. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn = new version
  • 33. Traditional Deployment ProblemsSlow, serial processInconsistent application stateFailures require high judgment decisions
  • 34. Availability  Zone  1 WWW1 WWW2 WWW3 WWWn Availability  Zone  2 WWW1 WWW2 WWW3 WWWnLoad  Balancer Availability  Zone  3 WWW1 WWW2 WWW3 WWWn
  • 35. Availability  Zone  1 Availability  Zone  1WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWnAvailability  Zone  2 Availability  Zone  2WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWn Load  BalancerAvailability  Zone  3 Availability  Zone  3WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWn = new version
  • 36. Availability  Zone  1 Availability  Zone  1WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWnAvailability  Zone  2 Availability  Zone  2WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWn Load  BalancerAvailability  Zone  3 Availability  Zone  3WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWn = new version
  • 37. Availability  Zone  1 Availability  Zone  1WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWnAvailability  Zone  2 Availability  Zone  2WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWn Load  BalancerAvailability  Zone  3 Availability  Zone  3WWW1 WWW2 WWW3 WWWn WWW1 WWW2 WWW3 WWWn = new version
  • 38. Blue-Green Deployment
  • 39. Amazon May Deployment Stats (production hosts & environments only) 11.6 seconds Mean time between deployments (typical weekday) 1,079 Max # of deployments in a single hour 10,000Mean # of hosts simultaneously receiving a deployment 30,000Max # of hosts simultaneously receiving a deployment
  • 40. Safe Deployment at AmazonRollbacks are done in 90% less time~99.999% successful deployments
  • 41. Cost of Mistakes
  • 42. New Metrics for CIOs Mean Time to Trafficdate host received first traffic – date host was ordered Mean Time to Deploy date code was deployed – date code was written Mean Time to Rollback time was rolled back – time code was deployed
  • 43. Consequences of lower mean time to:Traffic:Deploy:Rollback:
  • 44. Consequences of lower mean time to:Traffic: less Capex, less wasteDeploy:Rollback:
  • 45. Consequences of lower mean time to:Traffic: less Capex, less wasteDeploy: Developers work betterRollback:
  • 46. Consequences of lower mean time to:Traffic: less Capex, less wasteDeploy: Developers work betterRollback: less inconsistencies, downtime
  • 47. Conclusions
  • 48. EnterpriseCloudMigrationA perspective for CIOsSimone BrunozziAWS Technology Evangelist, APACTwitter - @simon - Tag: #awstour