Computers break. Software has bugs. Cloud services fail. And yet we don’t deal with failures very well. Why don’t we have better Plan B’s, for both personal and business uses of cloud? 

 SHOW: 576

CLOUD NEWS OF THE WEEK - http://bit.ly/cloudcast-cnotw

CHECK OUT OUR NEW PODCAST - "CLOUDCAST BASICS"

SHOW SPONSORS:

• JumpCloud (homepage)
• At the intersection of devices, identities, and access, JumpCloud’s cloud directory platform unifies the IT resources in any company’s infrastructure – anywhere work happens. Fully evaluate JumpCloud for free today
• Datadog Security Solution:  Modern Monitoring and Security - Datadog Application Monitoring: 
• Modern Application Performance Monitoring. Get started monitoring service dependencies to eliminate latency and errors and enhance your users experience with a free 14 day Datadog trial. Listeners of The Cloudcast will also receive a free Datadog T-shirt.

SHOW NOTES:

• AWS US-East-1 Outage (Dec.10,  2021) - Post Mortem (AWS Blog)
• AWS US-West outage (Dec.5, 2021)
• AWS is Too Big to Fail (The Information - Corey Quinn)
• YouTubeTV loses ESPN and other Disney channels (Dec.18, 2021)
• The Tech Industry after a Year of Burnout (The New Stack)

WHY DO WE EXPECT SO MUCH FROM COMPUTERS? 

While we have automated testing, test coverage, SLAs, redundancy best practices, etc - We still really don’t know when computers and software will break. So why do we get so frustrated when it happens, instead of having backup plans? 

SHOULD WE LOOK AT TECHNOLOGY FAILURES AS THE WORLD TRYING TO TELLING US SOMETHING?

1. Cloud service failures happen, and tend to last less than a full work day. Most are only a couple hours.
2. We tend to believe that we’re very dependent on technology and cloud services, until they go away. And then we figure out that we can all adapt. 
3. We could all use some time reading a book, getting outside to do some exercise (go for a walk), or spending some time away from computers or being online.
4. We could all use a break in our extended hours work days. 

FEEDBACK?

• Email: show at the cloudcast dot net
• Twitter: @thecloudcastnet