Dr. Werner Vogels Keynote


Published on

Keynote address and AWS overview by Dr. Werner Vogels, Amazon.com CTO, at the AWS Cloud for the Enterprise Event in LA on October 15, 2009 and in NY on October 19, 2009

Published in: Technology, Education
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Amazon Web Services is a set of primitive building blocks to enable developers to build applications and, ultimately, businesses, on our battle-tested infrastructure. So what kinds of building blocks do developers need? First, you need compute resources. The Elastic Compute Cloud, or EC2, allows developers to rent virtual computers, running in our data centers, and pay for them by the hour. Provision as many as you need – 1, 10, 1000, for as long as you need them, and you pay only for what you use (starting at 10 cents/hour). Next, you probably need somewhere to durably store and retrieve data. The Simple Storage Service, is, well, a simple storage service that allows to store and retrieve objects in the cloud using simple put and get API calls.You might need to index and query for that data, or create other structured data that you want to query, which is what we built SimpleDB.
  • Testing in the CloudInstant Test Labs in MinutesTesting as a ServiceVirtualization/AMIs for Reuse and ReprosWeb Services for AutomationOn-Demand Workforce of Testers (“Elastic QA Staff”)Client and Server Parallelization
  • Dr. Werner Vogels Keynote

    1. 1. Ahead in the Cloud<br />The power of Infrastructure as a Service<br />Dr. Werner Vogels<br />CTO, Amazon.com<br />
    2. 2. AWS - Amazon Web Services<br />Custom Applications and Services<br />Infrastructure as a Service<br />Database<br />Amazon SimpleDB<br />Content Delivery<br />Amazon CloudFront<br />Messaging<br />Amazon Simple Queue Service (SQS)<br />Payments<br />Amazon Flexible Payments Service (FPS)<br />On-Demand Workforce<br />Amazon Mechanical Turk<br />Parallel Processing<br />Amazon Elastic MapReduce<br />Compute<br />Amazon Elastic Compute Cloud (EC2)<br />Storage<br />Amazon Simple Storage Service (S3)<br />
    3. 3. Cloud Computing<br />On demand!<br />a style of computing where massively scalable IT-related capabilities are provided ‘as a service’ across the Internet to multiple external customers.<br />Pay as you Go<br />Gartner 2008<br />
    4. 4. Precusors<br />Distributed Computing<br />SaaS<br />Virtualization<br />SOA<br />
    5. 5. Forces Driving New Resource Models<br />Increasing Uncertainty<br />Growing Abundance<br />Intensifying Competition<br />Growing Power of Customers<br />Limited access to capital<br />From Push to Pull – Emerging Model for Mobilizing Resources – John Hagel & John Seely Brown - 2005<br />
    6. 6. Addressing Uncertainty<br />Acquire resources on demand<br />Release resources when no longer needed<br />Pay for what you use<br />Leverage other’s core competencies<br />Turn fixed cost into variable<br />
    7. 7.
    8. 8.
    9. 9.
    10. 10.
    11. 11. The 70/30 Switch<br />30% of time, energy and dollars <br />on differentiated value creation<br />70% of time, energy and dollars <br />on undifferentiated heavy lifting<br />
    12. 12. COMPUTE<br />MESSAGING<br />Amazon <br />EC2<br />Amazon <br />SQS<br />STORAGE<br />Amazon<br />EBS<br />Amazon <br />SimpleDB<br />Amazon <br />S3<br />
    13. 13. Amazon Infrastructure Services<br />
    14. 14.
    15. 15. Amazon Virtual Private Cloud (VPC)<br />
    16. 16. Lowers Cost<br />Eliminates Capital Investment<br />Reduces Operational Costs<br />Increases Agility<br />Reduce Time to Market<br />Removes contraints<br />Foundation for21st Century Architectures<br />Removes the “Heavy Lifting”<br />Leverages Scalability, Reliability and Security<br />
    17. 17. Billions of Objects in Amazon S3<br />
    18. 18. Enterprise Partners<br />
    19. 19. Cloud Services Ecosystem<br />
    20. 20. Eliminating Capital<br />
    21. 21. Time to Market<br />
    22. 22. Internet Scaling<br />
    23. 23. Scaling Computation<br />
    24. 24. Reliable Infrastructure<br />
    25. 25. Secure Infrastructure<br />
    26. 26. Lower Operational Cost<br />
    27. 27. Enterprise as a Platform<br />
    28. 28. Reserved Instances<br />for Amazon EC2<br />
    29. 29. Roadmap?<br />
    30. 30. SecurityScalability AvailabilityPerformanceCost-effectiveness<br />
    31. 31. http://aws.amazon.com<br />