Monkey Business For Serious Systems: Why chaos engineering isnt crazy

on YouTube ↗33m

" summary

A team starts with manual injections in a staging replica and later uses Litmus; deleting a proxy’s secret manager credentials causes database access failures that impact 3x more applications than anticipated, revealing hidden dependencies. Experiments include litmus chaos test-kill-pod runs that show containers terminate and recover with a measured 97 seconds restart, and deliberate attempts to break Litmus itself. Emphasis is on controlled execution, observable metrics, and using faults like deleted secret manager credentials to drive remediation.

AI-written summary · about

" chapters (12)

1. 0:00Chaos engineering intro
2. 2:10Chaos origins and Chaos Monkey
3. 3:56Personal Litmus journey
4. 5:21Why curiosity matters
5. 8:29CrowdStrike incident resilience
6. 12:23Why chaos isn’t crazy
7. 16:17Manual chaos experiments
8. 22:55Choosing Litmus
9. 25:47Controlled chaos cautions
10. 27:11Litmus dashboard walkthrough
11. 30:01Resiliency scores
12. 31:03Q&A

" related talks

• 30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos EngineeringSayan Mondal · stackconf 2023
• 01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failureAdrian Hornsby · NDC Oslo 2019
• 25mDestroy Your System To Make It More Reliable: An Easy Way To Start Chaos Engineering With LitmusChaoSayan Mondal · KubeCon + CloudNativeCon China 2025
• 57mChaos Engineering PrimerSergiu Bodiu · Voxxed Days Singapore 2017
• 46mDesigning a System for ChaosPaul Stack · DevConf 2019
• 37mCreating chaos in containersMaish Saidel-Keesing · Berlin Buzzwords 2023
• 28mChaos Engineering alongside Litmus and JenkinsAkram Riahi · Conf42 Chaos Engineering 2022
• 05mLightning Talk: Chaos Engineering In PracticePaul Jones · KubeCon + CloudNativeCon Europe 2018