Manu Mukerji @ Svcc 2011
Upcoming SlideShare
Loading in...5

Manu Mukerji @ Svcc 2011



How to not go down with AWS

How to not go down with AWS



Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

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.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Create apps that are stateless, the next step in the users flow shout not depend on going to the same serverIf you create the app to be server independent then working across multiple regions is simpleSmart monitoring: I prefer to keep my monitoring outside AWSCreate smart alerts (don’t send an email out if one server responded once over threshold, aws is notorious for network latencies) , Noisy neighbor issueDB independent design: for some app this is easier said than done, use memcached, deprecate features, use AJAX etcPause certain features, but not out of desperation plan for it.Use dns load balancing, when a user makes a request to your browser it first goes to a dns server and this responds with a set of ip addressesUse a CDN for static and maybe dynamic content

Manu Mukerji @ Svcc 2011 Manu Mukerji @ Svcc 2011 Presentation Transcript

  • Forbes February 17, 2010
    How to avoid going down
    along with AWS
    Manu Mukerji
    Chief Architect
  • Overview
    • AWS Infrastructure
    • What happened on April 21st (skynet)
    • Recommendations
    • Custom implementations?
  • AWS Infrastructure
    • Region vs. Availability Zone
    • EC2
    • S3
    • EBS
    • RDS
  • April 21st 2011 (Skynet)
    EBS Volumes “Stuck” in East
    Causing EC2 instances and RDS service to be unresponsive
    Read More
  • Recommendations
    • Design app to be server independent
    • Design app to work across multiple regions
    • Use smart monitoring scripts
    • Try to have a DB independent design
    • Decide which features to pause incase of a DB outage
    • Use Dynamic DNS/Load balancing
    • Use a CDN
  • Problems
    • There is no one method that works for everyone
    • In the cloud you determine the SLA you provide not AWS
    • It can get expensive
  • Additional Resources
    • AWS Architecture Center
  • Have Questions?
    Manu Mukerji
    Forbes February 17, 2010