Your SlideShare is downloading. ×
AWS Summit Nordics - Architecting for High Availability
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

AWS Summit Nordics - Architecting for High Availability

1,189
views

Published on

Published in: Travel, Business

0 Comments
9 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,189
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
91
Comments
0
Likes
9
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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

×