AWS Summit Nordics - Architecting for High Availability

1,630 views

Published on

Published in: Travel, Business

AWS Summit Nordics - Architecting for High Availability

  1. 1. Architecting For High Availability Guy Ernest Solutions Architect
  2. 2. 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
  3. 3. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. LOOSE COUPLING
  4. 4. #1 DESIGN FOR FAILURE ●○○○
  5. 5. « Everything fails all the time » Werner Vogels CTO of Amazon
  6. 6. AVOID SINGLE POINTS OF FAILURE
  7. 7. AVOID SINGLE POINTS OF FAILURE ASSUME EVERYTHING FAILS, AND WORK BACKWARDS
  8. 8. YOUR GOAL Applications should continue to function
  9. 9. HEALTH CHECKS
  10. 10. #2 MULTIPLE AVAILABILITY ZONES ●●○○
  11. 11. AVAILABILITY ZONES
  12. 12. 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)
  13. 13. AMAZON RDS MULTI-AZ
  14. 14. AMAZON ELB AND MULTIPLE AZs
  15. 15. #3 SCALING ●●●○
  16. 16. AMAZON CLOUDWATCH MONITORING FOR AWS RESOURCES
  17. 17. AUTO SCALING SCALE UP/DOWN EC2 CAPACITY
  18. 18. AUTO SCALING SCALE UP/DOWN EC2 CAPACITY
  19. 19. HEALTH CHECKS + AUTO SCALING
  20. 20. HEALTH CHECKS + AUTO SCALING = SELF-HEALING
  21. 21. #4 LOOSE COUPLING ●●●●
  22. 22. BUILD LOOSELY COUPLED SYSTEMS The looser they are coupled, the bigger they scale, the more fault tolerant they get…
  23. 23. PUBLISH & NOTIFY RECEIVE TRANSCODE
  24. 24. AMAZON SQS SIMPLE QUEUE SERVICE
  25. 25. PUBLISH & NOTIFY RECEIVE TRANSCODE
  26. 26. VISIBILITY TIMEOUT
  27. 27. BUFFERING
  28. 28. CLOUDWATCH METRICS FOR AMAZON SQS + AUTO SCALING
  29. 29. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. LOOSE COUPLING
  30. 30. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. LOOSE COUPLING
  31. 31. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. LOOSE COUPLING
  32. 32. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. LOOSE COUPLING
  33. 33. YOUR GOAL Applications should continue to function
  34. 34. IT’S ALL ABOUT CHOICE BALANCE COST & FAULT-TOLERANCE
  35. 35. 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

×