Architecting for High Availability
Joe Ziegler
Startup Business Development Manager APAC, AWS
July 18, 2013
@jiyosub
22
What is High Availability?
• Availability: Percentage of time an application operates during its work
cycle
• Loss of a...
33
Availability is related to
• Scalability
– Ability of an application to accommodate growth without changing design
– If...
AWS GLOBAL
INFRASTRUCTURE
US-WEST (Oregon)
EU-WEST (Ireland)
APAC (Tokyo)
APAC (Singapore)
US-WEST (N. California)
SOUTH AMERICA (Sao Paulo)
US-EAST...
US-WEST (Oregon))
EU-WEST (Ireland)
APAC (Tokyo)
US-WEST (N. California)
SOUTH AMERICA (Sao Paulo)
US-EAST (Virginia)
AWS ...
AWS BUILDING BLOCKS
Inherently Highly Available and
Fault Tolerant Services
Highly Available with
the right architecture
...
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
LET’S BUILD A
HIGHLY AVAILABLE
SYSTEM
#1
DESIGN FOR FAILURE
●○○○○
« Everything fails
all the time »
Werner Vogels
CTO of Amazon
AVOID SINGLE POINTS OF FAILURE
AVOID SINGLE POINTS OF FAILURE
ASSUME EVERYTHING FAILS,
AND WORK BACKWARDS
YOUR GOAL
Applications should continue to function
AMAZON EBS
ELASTIC BLOCK STORE
AMAZON ELB
ELASTIC LOAD BALANCING
HEALTH CHECKS
#2
MULTIPLE
AVAILABILITY ZONES
●●○○○
AMAZON RDS
MULTI-AZ
AMAZON ELB AND
MULTIPLE AZs
#3
SCALING
●●●○○
AUTO SCALING
SCALE UP/DOWN EC2 CAPACITY
#4
SELF-HEALING
●●●●○
HEALTH CHECKS
+
AUTO SCALING
HEALTH CHECKS
+
AUTO SCALING
=
SELF-HEALING
DEGRADED MODE
AMAZON S3
STATIC WEBSITE
+
AMAZON ROUTE 53
WEIGHTED RESOLUTION
#5
LOOSE
COUPLING
●●●●●
BUILD LOOSELY
COUPLED SYSTEMS
The looser they are coupled,
the bigger they scale,
the more fault tolerant they get…
AMAZON SQS
SIMPLE QUEUE SERVICE
PUBLISH&
NOTIFY
RECEIVE TRANSCODE
PUBLISH&
NOTIFY
RECEIVE TRANSCODE
VISIBILITY TIMEOUT
BUFFERING
CLOUDWATCH METRICS
FOR AMAZON SQS
+
AUTO SCALING
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
1. DESIGN FOR FAILURE
2. MULTIPLE AVAILABILITY ZONES
3. SCALING
4. SELF-HEALING
5. LOOSE COUPLING
YOUR GOAL
Applications should continue to function
IT’S ALL ABOUT
CHOICE
BALANCE COST & HIGH AVAILABILITY
AWS ARCHITECTURE CENTER
http://aws.amazon.com/architecture
AWS TECHNICAL ARTICLES
http://aws.amazon.com/articles
AWS BLOG
...
Technical Track
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
AWS Summit 2013 | Singapore - Architecting for High Availability
Upcoming SlideShare
Loading in …5
×

AWS Summit 2013 | Singapore - Architecting for High Availability

1,652 views

Published on

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.

Published in: Technology, Business
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,652
On SlideShare
0
From Embeds
0
Number of Embeds
441
Actions
Shares
0
Downloads
0
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

AWS Summit 2013 | Singapore - Architecting for High Availability

  1. 1. Architecting for High Availability Joe Ziegler Startup Business Development Manager APAC, AWS July 18, 2013 @jiyosub
  2. 2. 22 What is High Availability? • Availability: Percentage of time an application operates during its work cycle • Loss of availability is known as an outage or downtime – App is offline, unreachable, or partially available – App is slow to use – Planned and unplanned • Goal – No downtime – Always available
  3. 3. 33 Availability is related to • Scalability – Ability of an application to accommodate growth without changing design – If app cannot scale, availability may be impacted – Scalability doesn’t guarantee availability • Fault Tolerance – Built-in redundancy so apps can continue functioning when components fail – Fault tolerance is crucial to HA • Disaster Recovery – The process, policies, and procedures related to restoring service after a catastrophic event • AWS democratizes High Availability – Multiple servers, isolated redundant data centers, regions across the globe, FT services, etc.
  4. 4. AWS GLOBAL INFRASTRUCTURE
  5. 5. US-WEST (Oregon) EU-WEST (Ireland) APAC (Tokyo) APAC (Singapore) US-WEST (N. California) SOUTH AMERICA (Sao Paulo) US-EAST (Virginia) AWS GovCloud (US) APAC (Sydney) Regions
  6. 6. US-WEST (Oregon)) EU-WEST (Ireland) APAC (Tokyo) US-WEST (N. California) SOUTH AMERICA (Sao Paulo) US-EAST (Virginia) AWS GovCloud (US) APAC (Sydney) Availability Zones APAC (Singapore)
  7. 7. AWS BUILDING BLOCKS Inherently Highly Available and Fault Tolerant Services Highly Available with the right architecture  Amazon S3  Amazon DynamoDB  Amazon CloudFront  Amazon Route53  Elastic Load Balancing  Amazon SQS  Amazon SNS  Amazon SES  Amazon SWF  …  Amazon EC2  Amazon EBS  Amazon RDS  Amazon VPC
  8. 8. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  9. 9. LET’S BUILD A HIGHLY AVAILABLE SYSTEM
  10. 10. #1 DESIGN FOR FAILURE ●○○○○
  11. 11. « Everything fails all the time » Werner Vogels CTO of Amazon
  12. 12. AVOID SINGLE POINTS OF FAILURE
  13. 13. AVOID SINGLE POINTS OF FAILURE ASSUME EVERYTHING FAILS, AND WORK BACKWARDS
  14. 14. YOUR GOAL Applications should continue to function
  15. 15. AMAZON EBS ELASTIC BLOCK STORE
  16. 16. AMAZON ELB ELASTIC LOAD BALANCING
  17. 17. HEALTH CHECKS
  18. 18. #2 MULTIPLE AVAILABILITY ZONES ●●○○○
  19. 19. AMAZON RDS MULTI-AZ
  20. 20. AMAZON ELB AND MULTIPLE AZs
  21. 21. #3 SCALING ●●●○○
  22. 22. AUTO SCALING SCALE UP/DOWN EC2 CAPACITY
  23. 23. #4 SELF-HEALING ●●●●○
  24. 24. HEALTH CHECKS + AUTO SCALING
  25. 25. HEALTH CHECKS + AUTO SCALING = SELF-HEALING
  26. 26. DEGRADED MODE
  27. 27. AMAZON S3 STATIC WEBSITE + AMAZON ROUTE 53 WEIGHTED RESOLUTION
  28. 28. #5 LOOSE COUPLING ●●●●●
  29. 29. BUILD LOOSELY COUPLED SYSTEMS The looser they are coupled, the bigger they scale, the more fault tolerant they get…
  30. 30. AMAZON SQS SIMPLE QUEUE SERVICE
  31. 31. PUBLISH& NOTIFY RECEIVE TRANSCODE
  32. 32. PUBLISH& NOTIFY RECEIVE TRANSCODE
  33. 33. VISIBILITY TIMEOUT
  34. 34. BUFFERING
  35. 35. CLOUDWATCH METRICS FOR AMAZON SQS + AUTO SCALING
  36. 36. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  37. 37. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  38. 38. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  39. 39. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  40. 40. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  41. 41. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING
  42. 42. YOUR GOAL Applications should continue to function
  43. 43. IT’S ALL ABOUT CHOICE BALANCE COST & HIGH AVAILABILITY
  44. 44. 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
  45. 45. Technical Track

×