39

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

Embed Size (px)

DESCRIPTION

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.

Citation preview

Page 1: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 2: Amazon Web Services: Building a 'Web-Scale Computing' Architecture

Amazon Web Services: Building a 'Web-Scale Computing' ArchitectureJeff BarrSenior Web Services EvangelistAmazon Web Services

Page 3: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 4: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 5: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 6: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 7: Amazon Web Services: Building a 'Web-Scale Computing' Architecture

Problem

Your Idea

Successful Product

Hardware Costs

Software Costs

Costs to Run Idle Servers

Real Estate

Maintenance

Power

Cooling

Expertise

Load Balancing

Managing Growth

Bandwidth Management

Server Hosting

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

Dream or Nightmare?

Slashdot/Digg/TechCrunch EffectRapid, unexpected customer demand/growth

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

Seasonal Spikes

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

More Seasonal Spikes

“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

* http://news.com.com/2100-1038_3-6177341.html

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

The 70/30 Switch

30% of time, energy, and dollars on differentiated value creation

70% of time, energy, and dollars on undifferentiated heavy

lifting

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

Solution

Successful Product

Undifferentiated “Heavy Lifting”

Your Idea

Amazon Web Services

Amazon Simple Storage Service

Amazon Elastic Compute Cloud

Amazon Simple Queue Service

Amazon Mechanical Turk

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

Web-Scale Computing

Elastic capacity – both up and down

Fast

Always available

Rock-solid reliability

Very simple

Cost-effective

Low up-front investment

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

Business Results

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

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

Amazon Web Services

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

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

Amazon Simple Storage Service

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

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

Amazon S3 Pricing (As of June 1, 2007)

$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

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

Amazon Elastic Compute Cloud

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

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

Amazon Simple Queue Service

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

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

Amazon Mechanical Turk

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)

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

AWS Application Architecture

Page 22: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 23: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 24: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 25: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 26: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 27: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 28: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 29: Amazon Web Services: Building a 'Web-Scale Computing' Architecture
Page 30: Amazon Web Services: Building a 'Web-Scale Computing' Architecture

Smugmug.com

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

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

Smugmug’s Growth

Smugmug increased their photo storage from .5 million in 2003 to 140 million in 2007

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

Smugmug Economics*

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

* http://blogs.smugmug.com/don/files/ETech-SmugMug-Amazon-2007.pdf

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

GigaVox Media

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

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

GigaVox Infrastructure

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

GigaVox Economics

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

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

CastingWordsChallenge:

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

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

AWS Developer Support

Register at http://aws.amazon.com

Developer Forum

Getting Started Guides

Developer Tools

Code Samples

Newsletter

AWS Blog

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

Please fill out your eval

evaluation

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

© 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.