Manu Mukerji @ Svcc 2011

507 views

Published on

How to not go down with AWS

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
507
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • 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

    1. 1. Forbes February 17, 2010<br />How to avoid going down <br />along with AWS<br />@ShareThis<br />Manu Mukerji<br />Chief Architect<br />
    2. 2. Overview<br /><ul><li>AWS Infrastructure
    3. 3. What happened on April 21st (skynet)
    4. 4. Recommendations
    5. 5. Custom implementations?</li></li></ul><li>AWS Infrastructure<br /><ul><li>Region vs. Availability Zone
    6. 6. EC2
    7. 7. S3
    8. 8. EBS
    9. 9. RDS</li></li></ul><li>April 21st 2011 (Skynet)<br />EBS Volumes “Stuck” in East<br />Causing EC2 instances and RDS service to be unresponsive<br />Read More http://aws.amazon.com/message/65648/<br />
    10. 10. Recommendations<br /><ul><li>Design app to be server independent
    11. 11. Design app to work across multiple regions
    12. 12. Use smart monitoring scripts
    13. 13. Try to have a DB independent design
    14. 14. Decide which features to pause incase of a DB outage
    15. 15. Use Dynamic DNS/Load balancing
    16. 16. Use a CDN</li></li></ul><li>Problems<br /><ul><li>There is no one method that works for everyone
    17. 17. In the cloud you determine the SLA you provide not AWS
    18. 18. It can get expensive</li></li></ul><li>Additional Resources<br /><ul><li>AWS Architecture Center http://aws.amazon.com/architecture/</li></li></ul><li>Have Questions?<br />Manu Mukerji<br />next2manu@gmail.com<br />@next2manu<br />Forbes February 17, 2010<br />

    ×