Latest Amazon Outage and Designing for Failure

August 09 2011


I am getting really tired of people bashing the cloud by saying things like “Amazon’s outage in third day: debate over cloud computing’s future begins”. People need to understand that the cloud is not some magical place you put your applications into and never have to worry ever again. There are always a bunch of servers in racks somewhere or some power lines going to the data center, and there is always a driver that can run into a utility pole.

You can’t just put all responsibility into Amazon’s hands to keep your application online. All they do is provide flexible computing resources on demand in different regions and availability zones and provide 99.95% SLA at the most for their services.

Its your responsibility to design applications and systems architectures for failure, building in redundancy mostly at the application layer.

Here are some things you can do to design for failure on Amazon:

  1. Use multiples availability zones
  2. Use multiple regions
  3. Use database replication across availability zones or regions (MySQL or NoSQL)
  4. Have multiple servers on all tiers and spread them across availability zones
  5. Perform onsite and offsite backups
  6. Have a DR plan and an ability to launch on a different cloud

These are just a few. The point is you need to design your applications and systems architectures for HA in the cloud and not assume just because you are running in the cloud you are protected.

San Francisco


71 Stevenson St.

Suite 400

San Francisco, CA 94105

O: 1-888-991-2791

F: 1-415-655-6601


1400 16th Street,

Suite 400

Denver, CO 80202

O: 1-720-932-8028


2266 South Dobson Road

Suite 200

Mesa, AZ 85202

O: 1-480-603-3034


100 King Street West

Suite 5600

Toronto, Ontario, M5X 1C9

O: 1-416-479-5447

New York

165 Broadway, 23rd Floor

New York City, NY 10006

O: 1-646-759-3656

© 2017 ClearScale, LLC. All Rights Reserved.    About Us  |  Careers  |  Privacy Policy
live chat answering service