gistfile1.txt

Failure is Not Optional -- it will happen

http://highscalability.com/blog/2010/10/15/troubles-with-sharding-what-can-we-learn-from-the-foursquare.html
https://web.archive.org/web/20110209190434/http://blog.foursquare.com/2010/10/05/so-that-was-a-bummer/

https://www.joyent.com/blog/postmortem-for-outage-of-us-east-1-may-27-2014

https://aws.amazon.com/message/5467D2/

http://perfcap.blogspot.com/2012/11/cloud-outage-reports.html

https://en.wikipedia.org/wiki/5_Whys

http://www.kitchensoap.com/2014/11/14/the-infinite-hows-or-the-dangers-of-the-five-whys/

https://web.archive.org/web/20071114033455/http://www.rackspace.com/information/announcements/datacenter.php

https://wesabe.wordpress.com/2007/11/12/site-downtime-this-evening/


https://web.archive.org/web/20071114033455/http://www.rackspace.com/information/announcements/datacenter.php

https://aws.amazon.com/message/65648/

https://www.flickr.com/photos/kellan/6847621207
etsy - three-armed sweater
http://grant-pattishall-award.com/
http://bogan-martin-award.com/
http://www.indecorous.com/failure/

 [11:04 AM] 
 oooo, now that parse is shutting down, i could probably do some quality book reports on our post mortems too, from the perspective of “person who knew everything but selectively revealed some things due to Reasons"
 [11:05 AM] 
 it would be fascinating to do a convo-style review of old parse outage reports with someone who was a consumer of them
 [11:06 AM] 
 parse was an interesting place to write PMs for because our audience was largely engineers, but not engineers who knew jack shit about backend stuff and who thought database failures were unusual and terrifying