Adrian Hornsby Principal Technologist, Architecture @ Amazon Web Services (AWS) LinkedIn: https://www.linkedin.com/in/hornsby/ Architectures are growing increasingly distributed and hard to understand. As a result, software systems have become extremely difficult to debug and test, which increases the risk of failure. With these new challenges, chaos engineering ha become attractive to many organizations as a mechanism for underling the behavior of systems under expected circumstances. Whilst interest is growing, few have managed to build sustainable chaos engineering practices. In this talk, I will review the state of chaos engineering, the issues customers are facing, based on my learning as an AWS Solution Architect and Technologist focusing on Chaos Engineering and explain why I started to build tools to help with failure injection. — 0:00 Preamble 1:55 What prevents the wide adoption of chaos engineering? 2:54 Why is production chaos? 3:45 #0 - (Don't) call it (Chaos) Engineering 4:47 #1 - Look at the Bigger Picture 13:20 #2 - Change begins with understanding 24:30 #3 - Choose your Trojan Horse 28:16 #4 - Over-index on the Hypothesis 32:15 #5 - Introduce Chaos Engineering Early in the Journey 35:31 #6 - Blast-Radius Reduction Mindset 36:23 #7 - If you haven't verified it, its probably Broken 39:43 https://github.com/adhorn 40:50 Getting out of the starting blocks 43:46 Thank you! — 🥇 Gold Sponsors: ChaosIQ PagerDuty — Website 🚀🪐 https://www.conf42.com Reach out 📧📭 mark@conf42.com Conf42 Discord 🧑‍🤝‍🧑💬 https://discord.com/invite/dT6ZsFJ5ZM LinkedIn 👨‍💼💼 https://www.linkedin.com/company/49110720/ Twitter 🎵🐦https://twitter.com/conf42com Conf42Cast @ Spotify 🎧 https://tinyurl.com/bnyj6a8y