AWS provides a platform that is ideally suited for building highly available systems, enabling you to build reliable, affordable, fault-tolerant systems that operate with a minimal amount of human interaction. This session covers many of the high-availability and fault-tolerance concepts and features of the various services that you can use to build highly reliable and highly available applications in the AWS Cloud: architectures involving multiple Availability Zones, including EC2 best practices and RDS Multi-AZ deployments; loosely coupled and self-healing systems involving SQS and Auto Scaling; networking best practices for high availability, including Elastic IP addresses, load balancing, and DNS; leveraging services that inherently are built with high-availability and fault tolerance in mind, including S3, Elastic Beanstalk and more.

1. Carlos Conde
ARCHITECTING FOR HIGH
AVAILABILITY

2. AWS BUILDING BLOCKS
Inherently Fault-Tolerant
Services
Fault-Tolerant
with the right
architecture Amazon S3
 Amazon SimpleDB
 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
CloudSearch
 Amazon EC2
 Amazon EBS
 Amazon RDS
 Amazon VPC

7. #1
DESIGN FOR
FAILURE
●○○○

8. « Everything fails
all the time »
Werner Vogels
CTO of Amazon

9. YOUR GOAL:
Applications should continue to function even
if the underlying physical hardware fails or is
removed or replaced

10. AVOID SINGLE POINTS OF
FAILURE.
ASSUME EVERYTHING FAILS,
AND DESIGN BACKWARDS.

11. AVOID SINGLE POINTS OF
FAILURE.
ASSUME EVERYTHING FAILS,
AND DESIGN BACKWARDS.

17. HEALTH CHECKS

23. #2
USE MULTIPLE
AVAILABILITY ZONES

24. 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)

26. AMAZON RDS
MULTI-AZ

33. #3
BUILD FOR SCALE

44. HEALTH CHECKS
+
AUTO SCALING

49. HEALTH CHECKS
+
AUTO SCALING
=
SELF-HEALING

50. #4
LOOSE COUPLING

51. PUBLISH
& NOTIFY
RECEIVE TRANSCODE

52. PUBLISH
& NOTIFY
RECEIVE TRANSCODE

59. VISIBILITY
TIMEOUT

67. BUFFERING

73. CLOUDWATCH METRICS
FOR AMAZON SQS
+
AUTO SCALING

80. BUILD LOOSELY
COUPLED SYSTEMS
The looser they are coupled,
the bigger they scale,
the more fault tolerant they get…

81. 1. DESIGN FOR FAILURE
2. USE MULTI-AZ
3. BUILD FOR SCALE
4. DECOUPLE COMPONENTS

82. THANK YOU!