AWS re:Invent 2018: How AWS Minimizes the Blast Radius of Failures (ARC338)

At AWS, we obsess over operational excellence. We have a deep understanding of system availability, informed by over a decade of experience operating the cloud and our roots of operating Amazon.com for nearly a quarter-century. One thing we've learned is that failures come in many forms, some expected, and some unexpected. It's vital to build from the ground up and embrace failure. A core consideration is how to minimize the "blast radius" of any failures. In this talk, we discuss a range of blast radius reduction design techniques that we employ, including cell-based architecture, shuffle-sharding, availability zone independence, and region isolation. We also discuss how blast radius reduction infuses our operational practices.

[@lance2638]

cell based architecture starts at 21:07

[@jeevanullas]

If you want to watch and learn more about Shuffle Sharding start at 32:55

[@Steve-up3jp]

How do you handle database consistency if you have completely decoupled database in each cell?

[@paulschumann5257]

Absolutely clear overview of AWS blast radius. Very helpful abstract for reviewing for SAA exam.

[@move1649]

revisit after the incident...

[@hx5985]

Kinesis :)

[@guibirow]

The talk was too slow and made me watch it yawning a bit, but the content is really nice.

[@DollowAlbion]

Set playback speed to 1.5+ and enjoy

[@adityaakshay1]

This video hasn't aged well :)

[@lordlee6473]

Wow, this is one boring topic. I struggled to stay interested and engaged through the talk

[@nikhilagarwal8489]

It is tricky. You will like it more if you have experienced scaling pain-points.