Amazon Web Services: Building a 'Web-Scale Computing' Architecture


Published on

Building a reliable, flexible architecture that can manage the unpredictable nature of today's internet business is challenging. Jeff Barr, Evangelist for Amazon Web Services, will provide the blueprint for 'Web-Scale Computing' - enabling you to utilize Amazon Web Services to build an elastic architecture that can quickly respond to demand.

Published in: Technology
  • 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: Building a 'Web-Scale Computing' Architecture

  1. 1. Jeff Barr Senior Web Services Evangelist Amazon Web Services
  2. 2. Hardware Costs Successful Software Costs Your Idea Costs to Run Idle Servers Product Real Estate Maintenance Power Cooling Expertise Load Balancing Managing Growth Bandwidth Management Server Hosting
  3. 3. Slashdot/Digg/TechCrunch Effect Rapid, unexpected customer demand/growth
  4. 4. “Every year, we take the busiest minute of the busiest hour of the busiest day and build capacity on that, we built our systems to (handle that load) and we went above and beyond that.” * -- Scott Gulbransen Intuit Spokesman *
  5. 5. 30% of time, energy, and dollars on differentiated value creation 70% of time, energy, and dollars on undifferentiated heavy lifting
  6. 6. Successful Undifferentiated Your Idea Product “Heavy Lifting” Amazon Web Services Amazon Simple Storage Service Amazon Elastic Compute Cloud Amazon Simple Queue Service Amazon Mechanical Turk
  7. 7. Elastic capacity – both up and down Fast Always available Rock-solid reliability Very simple Cost-effective Low up-front investment
  8. 8. Faster time to market Ability to scale on demand Focus on product & core competencies More capital available to drive business Faster pace of innovation Happy investors
  9. 9. 10 web services spanning core infrastructure to e- commerce Running as part of Amazon’s proven computing and networking environment 12 years and $2 Billion spent building Amazon’s technology, infrastructure & content 240K registered developers
  10. 10. Amazon S3: Storage for the internet Store 1 byte to 5 GB objects, URL-accessible SOAP and REST APIs Private and Public Storage Options (ACLs) Economical
  11. 11. $0.15 per GB per month to store data $0.10 - $0.18 per GB to transfer data $.0001 - $.01 per request Paid via AWS Developer account
  12. 12. Amazon EC2: Compute capacity in the cloud Scale capacity up and down in minutes Developers control their machine instances $0.10 per server per hour $0.10 - $0.18 per GB to transfer data
  13. 13. Amazon SQS: Message queuing service Reliable message transmission & storage to avoid duplication or lost messages Unlimited queue count, message size, message count $0.10 per 1,000 messages sent $0.10 - $0.18 per GB to transfer data
  14. 14. API to Human Processing Power Planetary-scale Paid Work Force Put a Human in the Loop HITs, Requesters, Workers 10% fee to Amazon ($0.005 minimum)
  15. 15. Challenge: Scalable storage solution to meet increasing customer demand Solution: Amazon S3 Result: 192TB stored in Amazon S3, saved $1,000,000 Time to Deploy: One week to start storing photos
  16. 16. Smugmug increased their photo storage from .5 million in 2003 to 140 million in 2007
  17. 17. Implemented Amazon S3 in April 2006 Apr-Oct grew 72%, from 64 Million images to 110 Million images Currently storing 192 TB in Amazon S3 Estimates saving $1,000,000 to date Project $1-2 Million savings in 2007 * 2007.pdf
  18. 18. Challenge: Needed scalable support for services such as transcoding and file transfer Solution: Amazon S3, Amazon EC2, and Amazon SQS Result: $100 to launch scalable infrastructure Time to Deploy: 1 day to integrate Amazon S3, 75 days from start time to full launch w/ all services
  19. 19. GigaVox Infrastructure
  20. 20. Implemented Amazon S3, Amazon EC2 and Amazon SQS in November 2006 Created an infinitely scalable infrastructure for less than $100 - building the same infrastructure themselves would have cost thousands of dollars Reduced staffing requirements - far less responsibility for 24x7 operations
  21. 21. Challenge: Provide an inexpensive podcast transcription service to customers via the Internet Solution: Amazon Mechanical Turk Result: Able to emerge as the market leader with low prices and quick turnarounds Time to Deploy: 24 days
  22. 22. Register at Developer Forum Getting Started Guides Developer Tools Code Samples Newsletter AWS Blog
  23. 23. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.