amazon.com s Journey to the Cloud Jon Jenkins AWS Summit June 13, 2011

Transcription

1 amazon.com s Journey to the Cloud Jon Jenkins jjenkin@amazon.com AWS Summit June 13, 2011

2

3

4

5 +

6 First real data center

7

8 Distribution Center Isolation

9

10 Decouple Service Oriented Architecture Scale Horizontally Increase Speed of Execution Develop Iteratively Seek Simplicity

11

12 What could we do with just S3?

13

14 IMDB Widget Architecture Amazon Amazon Web Server IMDB Customer Service Call IMDB Service IMDB Database Render Process

15 The Problem Release process is coupled Runtime latency & scale requirements Service integration issues Use S3 as a service The Solution Store raw HTML for the feature in S3

16 Amazon Before Amazon Web Server IMDB Customer Service Call IMDB Service IMDB Database Render Process After Amazon Amazon Web Server IMDB Customer Generic S3 HTML Puller S3 HTML Store

17 Results Reduced page latency IMDB doesn t worry about scaling Reduced web server CPU utilization Improved availability through reduced dependencies Simplified release model AJAX readiness

18 What about a more complex case?

19

20 The Problem The system has lots of moving parts It must run in an external data center It must scale up quickly Development team is two people The Solution Use as many AWS services as possible

21 Config Store SQS CloudWatch (latency, test case results, status codes) Alarm Rule Engines Web Portal Configuration Scheduler (primary/ secondary) Agents EC2 S3 Notification EC2... SDB Web Service EC2 RDS

22 Results Very few dev resources required Launched without having to negotiate any new datacenter co-lo presence True external performance metrics We can test site features in development that have not yet launched The system scales horizontally to large amounts of traffic

23 What about amazon.com web servers?

24 Typical Weekly Traffic to amazon.com Sunday Monday Tuesday Wednesday Thursday Friday Saturday

25 Typical Weekly Traffic to amazon.com Sunday Monday Tuesday Wednesday Thursday Friday Saturday

26 Typical Weekly Traffic to amazon.com 39% 61% Sunday Monday Tuesday Wednesday Thursday Friday Saturday

27 November Traffic for amazon.com

28 November Traffic for amazon.com 76% 24%

29 The Problem Retail web site hardware is underutilized Traffic spikes require heroic effort Scaling is non-linear The Solution Migrate the entire web server fleet to AWS

30 amazon.com AWS Availability Zone 1 Customer Load Balancer EC2 www Availability Zone N EC2 www N VPC Databases Services EC2 www 1 EC2 www N...

31 November 10, 2010

32 Results All traffic for is now served from AWS We can dynamically scale the fleet in increments as small as a single host Traffic spikes can be handled with ease

33 What about a DB use case?

34

35 Basic Order Storage Architecture Order Database Web Servers Ordering Service

36 Basic Order Storage Architecture Order Database Web Servers Ordering Service Scaling Pattern 1 Scaling Pattern 2 Order Database Order Database Web Servers Ordering Service Web Servers Ordering Service

37 The Problem Cumulative data impacts scale No database scaling pattern is ideal Databases infrastructure is expensive The Solution Create a tiered storage system with AWS

38 Order Database Web Servers Ordering Service S3

39 Results 670 million (4TB) orders now stored in S3 We are spending way less on DB hosts Sets us up for migration to RDS / SDB

40 Lessons learned

41 Business Lessons Less time spent on capacity planning Fewer conversations with finance More innovation Happier developers I get credit for AWS price reductions Be sure to consider compliance issues No more lease returns!

42 Technical Lessons Start with simple applications Iterate toward your desired end-state Identify reusable components Engage security early and treat them as partners Migrate to the cloud in concert with your other architectural objectives The cloud can t cover up sloppy engineering

43 Q&A