aws summit nordics - architecting for high availability

109
Architecting For High Availability Guy Ernest Solutions Architect

Upload: amazon-web-services

Post on 20-Jun-2015

1.229 views

Category:

Travel


4 download

TRANSCRIPT

Page 1: AWS Summit Nordics - Architecting for High Availability

Architecting For High Availability

Guy Ernest

Solutions Architect

Page 2: AWS Summit Nordics - Architecting for High Availability
Page 3: AWS Summit Nordics - Architecting for High Availability
Page 4: AWS Summit Nordics - Architecting for High Availability

AWS BUILDING BLOCKS Inherently Fault-Tolerant

Services Fault-Tolerant with the

right architecture Amazon S3

Amazon DynamoDB

Amazon CloudFront

Amazon SWF

Amazon SQS

Amazon SNS

Amazon SES

Amazon Route53

Elastic Load Balancing

AWS IAM

AWS Elastic Beanstalk

Amazon

ElastiCache

Amazon EMR

Amazon Redshift

Amazon CloudSearch

Amazon EC2

Amazon EBS

Amazon RDS

Amazon VPC

Page 5: AWS Summit Nordics - Architecting for High Availability
Page 6: AWS Summit Nordics - Architecting for High Availability
Page 7: AWS Summit Nordics - Architecting for High Availability
Page 8: AWS Summit Nordics - Architecting for High Availability
Page 9: AWS Summit Nordics - Architecting for High Availability

1. DESIGN FOR FAILURE

2. MULTIPLE AVAILABILITY ZONES

3. SCALING

4. LOOSE COUPLING

Page 10: AWS Summit Nordics - Architecting for High Availability

#1 DESIGN FOR FAILURE

●○○○

Page 11: AWS Summit Nordics - Architecting for High Availability

« Everything fails all the time »

Werner Vogels

CTO of Amazon

Page 12: AWS Summit Nordics - Architecting for High Availability

AVOID SINGLE POINTS OF FAILURE

Page 13: AWS Summit Nordics - Architecting for High Availability

AVOID SINGLE POINTS OF FAILURE

ASSUME EVERYTHING FAILS,

AND WORK BACKWARDS

Page 14: AWS Summit Nordics - Architecting for High Availability

YOUR GOAL

Applications should continue to function

Page 15: AWS Summit Nordics - Architecting for High Availability
Page 16: AWS Summit Nordics - Architecting for High Availability
Page 17: AWS Summit Nordics - Architecting for High Availability
Page 18: AWS Summit Nordics - Architecting for High Availability
Page 19: AWS Summit Nordics - Architecting for High Availability
Page 20: AWS Summit Nordics - Architecting for High Availability

HEALTH CHECKS

Page 21: AWS Summit Nordics - Architecting for High Availability
Page 22: AWS Summit Nordics - Architecting for High Availability
Page 23: AWS Summit Nordics - Architecting for High Availability
Page 24: AWS Summit Nordics - Architecting for High Availability
Page 25: AWS Summit Nordics - Architecting for High Availability
Page 26: AWS Summit Nordics - Architecting for High Availability

#2 MULTIPLE

AVAILABILITY ZONES ●●○○

Page 27: AWS Summit Nordics - Architecting for High Availability

AVAILABILITY ZONES

Page 28: AWS Summit Nordics - Architecting for High Availability

US-WEST (N. California) EU-WEST (Ireland)

ASIA PAC (Tokyo)

ASIA PAC

(Singapore)

US-WEST (Oregon)

SOUTH AMERICA (Sao Paulo)

US-EAST (Virginia)

GOV CLOUD

ASIA PAC (Sidney)

Page 29: AWS Summit Nordics - Architecting for High Availability
Page 30: AWS Summit Nordics - Architecting for High Availability

AMAZON RDS

MULTI-AZ

Page 31: AWS Summit Nordics - Architecting for High Availability
Page 32: AWS Summit Nordics - Architecting for High Availability
Page 33: AWS Summit Nordics - Architecting for High Availability
Page 34: AWS Summit Nordics - Architecting for High Availability
Page 35: AWS Summit Nordics - Architecting for High Availability
Page 36: AWS Summit Nordics - Architecting for High Availability
Page 37: AWS Summit Nordics - Architecting for High Availability

AMAZON ELB AND

MULTIPLE AZs

Page 38: AWS Summit Nordics - Architecting for High Availability
Page 39: AWS Summit Nordics - Architecting for High Availability
Page 40: AWS Summit Nordics - Architecting for High Availability

#3 SCALING

●●●○

Page 41: AWS Summit Nordics - Architecting for High Availability
Page 42: AWS Summit Nordics - Architecting for High Availability

AMAZON CLOUDWATCH MONITORING FOR AWS RESOURCES

Page 43: AWS Summit Nordics - Architecting for High Availability
Page 44: AWS Summit Nordics - Architecting for High Availability

AUTO SCALING SCALE UP/DOWN EC2 CAPACITY

Page 45: AWS Summit Nordics - Architecting for High Availability
Page 46: AWS Summit Nordics - Architecting for High Availability
Page 47: AWS Summit Nordics - Architecting for High Availability
Page 48: AWS Summit Nordics - Architecting for High Availability
Page 49: AWS Summit Nordics - Architecting for High Availability
Page 50: AWS Summit Nordics - Architecting for High Availability
Page 51: AWS Summit Nordics - Architecting for High Availability
Page 52: AWS Summit Nordics - Architecting for High Availability
Page 53: AWS Summit Nordics - Architecting for High Availability
Page 54: AWS Summit Nordics - Architecting for High Availability

AUTO SCALING SCALE UP/DOWN EC2 CAPACITY

Page 55: AWS Summit Nordics - Architecting for High Availability
Page 56: AWS Summit Nordics - Architecting for High Availability
Page 57: AWS Summit Nordics - Architecting for High Availability
Page 58: AWS Summit Nordics - Architecting for High Availability
Page 59: AWS Summit Nordics - Architecting for High Availability
Page 60: AWS Summit Nordics - Architecting for High Availability
Page 61: AWS Summit Nordics - Architecting for High Availability
Page 62: AWS Summit Nordics - Architecting for High Availability
Page 63: AWS Summit Nordics - Architecting for High Availability

HEALTH CHECKS

+ AUTO SCALING

Page 64: AWS Summit Nordics - Architecting for High Availability
Page 65: AWS Summit Nordics - Architecting for High Availability
Page 66: AWS Summit Nordics - Architecting for High Availability
Page 67: AWS Summit Nordics - Architecting for High Availability
Page 68: AWS Summit Nordics - Architecting for High Availability

HEALTH CHECKS

+ AUTO SCALING

=

SELF-HEALING

Page 69: AWS Summit Nordics - Architecting for High Availability
Page 70: AWS Summit Nordics - Architecting for High Availability

#4 LOOSE

COUPLING ●●●●

Page 71: AWS Summit Nordics - Architecting for High Availability

BUILD LOOSELY COUPLED SYSTEMS

The looser they are coupled, the bigger they scale,

the more fault tolerant they get…

Page 72: AWS Summit Nordics - Architecting for High Availability
Page 73: AWS Summit Nordics - Architecting for High Availability
Page 74: AWS Summit Nordics - Architecting for High Availability

PUBLISH

& NOTIFY RECEIVE TRANSCODE

Page 75: AWS Summit Nordics - Architecting for High Availability

AMAZON SQS SIMPLE QUEUE SERVICE

Page 76: AWS Summit Nordics - Architecting for High Availability

PUBLISH

& NOTIFY RECEIVE TRANSCODE

Page 77: AWS Summit Nordics - Architecting for High Availability
Page 78: AWS Summit Nordics - Architecting for High Availability
Page 79: AWS Summit Nordics - Architecting for High Availability
Page 80: AWS Summit Nordics - Architecting for High Availability
Page 81: AWS Summit Nordics - Architecting for High Availability
Page 82: AWS Summit Nordics - Architecting for High Availability
Page 83: AWS Summit Nordics - Architecting for High Availability

VISIBILITY TIMEOUT

Page 84: AWS Summit Nordics - Architecting for High Availability
Page 85: AWS Summit Nordics - Architecting for High Availability
Page 86: AWS Summit Nordics - Architecting for High Availability
Page 87: AWS Summit Nordics - Architecting for High Availability
Page 88: AWS Summit Nordics - Architecting for High Availability
Page 89: AWS Summit Nordics - Architecting for High Availability
Page 90: AWS Summit Nordics - Architecting for High Availability
Page 91: AWS Summit Nordics - Architecting for High Availability

BUFFERING

Page 92: AWS Summit Nordics - Architecting for High Availability
Page 93: AWS Summit Nordics - Architecting for High Availability
Page 94: AWS Summit Nordics - Architecting for High Availability
Page 95: AWS Summit Nordics - Architecting for High Availability
Page 96: AWS Summit Nordics - Architecting for High Availability
Page 97: AWS Summit Nordics - Architecting for High Availability
Page 98: AWS Summit Nordics - Architecting for High Availability

CLOUDWATCH METRICS FOR AMAZON SQS

+ AUTO SCALING

Page 99: AWS Summit Nordics - Architecting for High Availability
Page 100: AWS Summit Nordics - Architecting for High Availability
Page 101: AWS Summit Nordics - Architecting for High Availability
Page 102: AWS Summit Nordics - Architecting for High Availability
Page 103: AWS Summit Nordics - Architecting for High Availability

1. DESIGN FOR FAILURE

2. MULTIPLE AVAILABILITY ZONES

3. SCALING

4. LOOSE COUPLING

Page 104: AWS Summit Nordics - Architecting for High Availability

1. DESIGN FOR FAILURE

2. MULTIPLE AVAILABILITY ZONES

3. SCALING

4. LOOSE COUPLING

Page 105: AWS Summit Nordics - Architecting for High Availability

1. DESIGN FOR FAILURE

2. MULTIPLE AVAILABILITY ZONES

3. SCALING

4. LOOSE COUPLING

Page 106: AWS Summit Nordics - Architecting for High Availability

1. DESIGN FOR FAILURE

2. MULTIPLE AVAILABILITY ZONES

3. SCALING

4. LOOSE COUPLING

Page 107: AWS Summit Nordics - Architecting for High Availability

YOUR GOAL

Applications should continue to function

Page 108: AWS Summit Nordics - Architecting for High Availability

IT’S ALL ABOUT

CHOICE BALANCE COST & FAULT-TOLERANCE

Page 109: AWS Summit Nordics - Architecting for High Availability

AWS ARCHITECTURE CENTER http://aws.amazon.com/architecture

AWS TECHNICAL ARTICLES http://aws.amazon.com/articles

AWS BLOG http://aws.typepad.com

AWS PODCAST http://aws.amazon.com/podcast