architecting for high availability
play

Architecting for High Availability Attila Narin AWS Solutions - PowerPoint PPT Presentation

Architecting for High Availability Attila Narin AWS Solutions Architecture QCon London, March 2013 Session Feedback ID 1927 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING LETS BUILD A SYSTEM


  1. Architecting for High Availability Attila Narin AWS Solutions Architecture QCon London, March 2013 Session Feedback ID 1927

  2. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING

  3. LET’S BUILD A SYSTEM

  4. HIGHLY AVAILABLE LET’S BUILD A SYSTEM

  5. AWS BUILDING BLOCKS Inherently Highly Available Highly Available with and Fault Tolerant Services the right architecture  Amazon S3  Amazon SQS Amazon EC2    Amazon Amazon SNS Amazon EBS  DynamoDB  Amazon SES Amazon RDS   Amazon  Amazon SWF Amazon VPC CloudFront   …  Amazon Route53  Elastic Load Balancing

  6. AWS BUILDING BLOCKS Inherently Highly Available Highly Available with and Fault Tolerant Services the right architecture  Amazon S3  Amazon SQS Amazon EC2    Amazon Amazon SNS Amazon EBS  DynamoDB  Amazon SES Amazon RDS   Amazon  Amazon SWF Amazon VPC CloudFront   …  Amazon Route53  Elastic Load Balancing

  7. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING

  8. DESIGN FOR FAILURE ●○○○○ #

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

  10. AVOID SINGLE POINTS OF FAILURE

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

  12. YOUR GOAL Applications should continue to function

  13. AMAZON EBS ELASTIC BLOCK STORE

  14. AMAZON ELB ELASTIC LOAD BALANCING

  15. HEALTH CHECKS

  16. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING

  17. AVAILABILITY MULTIPLE ZONES ●●○○○ #

  18. AVAILABILITY ZONES

  19. US-WEST (N. California) EU-WEST (Ireland) GOV CLOUD ASIA PAC (Tokyo) US-EAST (Virginia) ASIA PAC (Sidney) US-WEST (Oregon) ASIA PAC (Singapore) SOUTH AMERICA (Sao Paulo)

  20. US-WEST (N. California) EU-WEST (Ireland) GOV CLOUD ASIA PAC (Tokyo) US-EAST (Virginia) ASIA PAC (Sidney) US-WEST (Oregon) ASIA PAC (Singapore) SOUTH AMERICA (Sao Paulo)

  21. AMAZON RDS MULTI-AZ

  22. AMAZON ELB AND MULTIPLE AZs

  23. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING

  24. SCALING ●●●○○ #

  25. AUTO SCALING SCALE UP/DOWN EC2 CAPACITY

  26. UNEXPECTED SPIKES

  27. EXPECTED SPIKES

  28. DATA TIER

  29. AWS BUILDING BLOCKS Inherently Highly Available Highly Available with and Fault Tolerant Services the right architecture  Amazon S3  Amazon SQS Amazon EC2    Amazon Amazon SNS Amazon EBS  DynamoDB  Amazon SES Amazon RDS   Amazon  Amazon SWF Amazon VPC CloudFront   …  Amazon Route53  Elastic Load Balancing

  30. AWS BUILDING BLOCKS Inherently Highly Available Highly Available with and Fault Tolerant Services the right architecture  Amazon S3  Amazon SQS Amazon EC2    Amazon Amazon SNS Amazon EBS  DynamoDB  Amazon SES Amazon RDS   Amazon  Amazon SWF Amazon VPC CloudFront   …  Amazon Route53  Elastic Load Balancing

  31. AMAZON S3 SIMPLE STORAGE SERVICE

  32. 99.999999999 % DURABILITY

  33. SCALABLE & AVAILABLE NO CAPACITY PLANNING REQUIRED

  34. ZERO ADMINISTRATION

  35. AWS BUILDING BLOCKS Inherently Highly Available Highly Available with and Fault Tolerant Services the right architecture  Amazon S3  Amazon SQS Amazon EC2    Amazon Amazon SNS Amazon EBS  DynamoDB  Amazon SES Amazon RDS   Amazon  Amazon SWF Amazon VPC CloudFront   …  Amazon Route53  Elastic Load Balancing

  36. AMAZON DYNAMODB HIGH-PERFORMANCE, FULLY MANAGED NoSQL DATABASE SERVICE

  37. LOW LATENCY AVERAGE READS < 5 MS , WRITES < 10 MS

  38. PREDICTABLE PERFORMANCE PROVISIONES THROUGHPUT

  39. SEAMLESS SCALABILITY LIVE REPARTITIONING

  40. ZERO ADMINISTRATION

  41. AWS BUILDING BLOCKS Inherently Highly Available Highly Available with and Fault Tolerant Services the right architecture  Amazon S3  Amazon SQS Amazon EC2    Amazon Amazon SNS Amazon EBS  DynamoDB  Amazon SES Amazon RDS   Amazon  Amazon SWF Amazon VPC CloudFront   …  Amazon Route53  Elastic Load Balancing

  42. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING

  43. SELF-HEALING ●●●●○ #

  44. HEALTH CHECKS + AUTO SCALING

  45. HEALTH CHECKS + AUTO SCALING = SELF- HEALING

  46. DEGRADED MODE

  47. AMAZON S3 STATIC WEBSITE + AMAZON ROUTE53 WEIGHTED RESOLUTION

  48. 1. DESIGN FOR FAILURE 2. MULTIPLE AVAILABILITY ZONES 3. SCALING 4. SELF-HEALING 5. LOOSE COUPLING

  49. COUPLING LOOSE ●●●●● #

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

  51. AMAZON SQS SIMPLE QUEUE SERVICE

  52. PUBLISH RECEIVE TRANSCODE & NOTIFY

  53. PUBLISH RECEIVE TRANSCODE & NOTIFY

Recommend


More recommend