1.
Carlos CondeARCHITECTING FOR HIGHAVAILABILITY

2.
AWS BUILDING BLOCKSInherently Fault-TolerantServicesFault-Tolerantwith the rightarchitecture Amazon S3 Amazon SimpleDB Amazon DynamoDB Amazon CloudFront Amazon SWF Amazon SQS Amazon SNS Amazon SES Amazon Route53 Elastic LoadBalancing AWS IAM AWS ElasticBeanstalk AmazonElastiCache Amazon EMR AmazonCloudSearch Amazon EC2 Amazon EBS Amazon RDS Amazon VPC

3.
#1DESIGN FORFAILURE●○○○

4.
« Everything failsall the time »Werner VogelsCTO of Amazon

5.
YOUR GOAL:Applications should continue to function evenif the underlying physical hardware fails or isremoved or replaced

6.
AVOID SINGLE POINTS OFFAILURE.ASSUME EVERYTHING FAILS,AND DESIGN BACKWARDS.

7.
AVOID SINGLE POINTS OFFAILURE.ASSUME EVERYTHING FAILS,AND DESIGN BACKWARDS.

8.
HEALTH CHECKS

9.
#2USE MULTIPLEAVAILABILITY ZONES

10.
US-WEST (Oregon))EU-WEST (Ireland)ASIA PAC (Tokyo)ASIA PAC(Singapore)US-WEST (N. California)SOUTH AMERICA (Sao Paulo)US-EAST (Virginia)AWS GovCloud (US)ASIA PAC (Sydney)

11.
AMAZON RDSMULTI-AZ

12.
#3BUILD FOR SCALE

13.
HEALTH CHECKS+AUTO SCALING

14.
HEALTH CHECKS+AUTO SCALING=SELF-HEALING

15.
#4LOOSE COUPLING

16.
PUBLISH& NOTIFYRECEIVE TRANSCODE

17.
PUBLISH& NOTIFYRECEIVE TRANSCODE

18.
VISIBILITYTIMEOUT

19.
BUFFERING

20.
CLOUDWATCH METRICSFOR AMAZON SQS+AUTO SCALING

21.
BUILD LOOSELYCOUPLED SYSTEMSThe looser they are coupled,the bigger they scale,the more fault tolerant they get…

22.
1. DESIGN FOR FAILURE2. USE MULTI-AZ3. BUILD FOR SCALE4. DECOUPLE COMPONENTS

23.
THANK YOU!