AWS had an outage in a region and many people responded. What did we learn about outages, responses, and dealing with cloud services going forward?
SHOW: 574
CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw
CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"
SHOW SPONSORS:
SHOW NOTES:
CLOUD OUTAGES ARE A PART OF USING A SHARED SERVICE
This week another major cloud service had an outage. They happen frequently enough, for some period of time (usually measured in hours), that we really notice them and then move on. Their impact is felt across many sites and dependent services,
SOME THOUGHTS ON RESPONSES TO CLOUD OUTAGES
- 5 levels of grief - denial and isolation, anger, bargaining, depression, and acceptance.
- The cloud providers (typically) don’t snipe at either other - they’ve all been there.
- The post-mortems are becoming more consistent - any highly anticipated
- We continue to learn about differences in cloud architectures, and where failures points (and failure actions) occur.
- We still don’t understand the internal cloud architectural dependencies of each cloud.
- How many companies actually follow multi-region best practices? How much does multi-region cost?
- Multi-cloud is often a knee-jerk reaction, but it’s never that simple - cost, complexity, skills
FEEDBACK?
