• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
AWS Summit 2013 | Auckland - Architecting for High Availability
 

AWS Summit 2013 | Auckland - Architecting for High Availability

on

  • 1,356 views

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

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.

Statistics

Views

Total Views
1,356
Views on SlideShare
1,155
Embed Views
201

Actions

Likes
8
Downloads
0
Comments
0

3 Embeds 201

http://www.scoop.it 198
http://10.41.128.50 2
http://webcache.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    AWS Summit 2013 | Auckland - Architecting for High Availability AWS Summit 2013 | Auckland - Architecting for High Availability Presentation Transcript

    • John HildebrandtArchitecting for High AvailabilitySolutions Architect, AWS
    • 22What is High Availability?• Availability: Percentage of time an application operates during its workcycle• 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
    • 33Availability 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• AWS democratizes High Availability– Multiple servers, isolated redundant data centers, regions across the globe, FT services, etc.
    • AWS GLOBALINFRASTRUCTURE
    • 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)Regions
    • 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)Availability Zones
    • AWS BUILDING BLOCKSInherently Highly Available andFault Tolerant ServicesHighly Available withthe 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
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • LET’S BUILD AHIGHLY AVAILABLESYSTEM
    • #1DESIGN FOR FAILURE●○○○○
    • « Everything failsall the time »Werner VogelsCTO of Amazon
    • AVOID SINGLE POINTS OF FAILURE
    • AVOID SINGLE POINTS OF FAILUREASSUME EVERYTHING FAILS,AND WORK BACKWARDS
    • YOUR GOALApplications should continue to function
    • AMAZON EBSELASTIC BLOCK STORE
    • AMAZON ELBELASTIC LOAD BALANCING
    • HEALTH CHECKS
    • #2MULTIPLEAVAILABILITY ZONES●●○○○
    • AMAZON RDSMULTI-AZ
    • AMAZON ELB ANDMULTIPLE AZs
    • #3SCALING●●●○○
    • AUTO SCALINGSCALE UP/DOWN EC2 CAPACITY
    • #4SELF-HEALING●●●●○
    • HEALTH CHECKS+AUTO SCALING
    • HEALTH CHECKS+AUTO SCALING=SELF-HEALING
    • #5LOOSECOUPLING●●●●●
    • BUILD LOOSELYCOUPLED SYSTEMSThe looser they are coupled,the bigger they scale,the more fault tolerant they get…
    • AMAZON SQSSIMPLE QUEUE SERVICE
    • PUBLISH&NOTIFYRECEIVE TRANSCODE
    • PUBLISH&NOTIFYRECEIVE TRANSCODE
    • VISIBILITY TIMEOUT
    • BUFFERING
    • CLOUDWATCH METRICSFOR AMAZON SQS+AUTO SCALING
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • 1. DESIGN FOR FAILURE2. MULTIPLE AVAILABILITY ZONES3. SCALING4. SELF-HEALING5. LOOSE COUPLING
    • YOUR GOALApplications should continue to function
    • IT’S ALL ABOUTCHOICEBALANCE COST & HIGH AVAILABILITY
    • AWS ARCHITECTURE CENTERhttp://aws.amazon.com/architectureAWS TECHNICAL ARTICLEShttp://aws.amazon.com/articlesAWS BLOGhttp://aws.typepad.comAWS PODCASThttp://aws.amazon.com/podcast