Fostering Chaos Engineering Culture
summary
Describes building an agentless chaos tool (Java + Node.js) that integrates with CI/CD and reuses Splunk for telemetry, lets teams define component-specific actions (Tomcat, Cassandra, MongoDB), schedule or trigger experiments, and view run history. Workflow enforces steady state → hypothesis → inject failure → validate. Runs in preprod then small production blast radii. Experiments uncover real vendor defects (Google, Oracle, load balancer) and the in-house tool proves useful with open source planned for wider use.
AI-written summary · about
chapters (7)
- 0:00Introduction to talk
- 1:26What is resiliency
- 3:57Defining chaos engineering
- 7:50Chaos testing four steps
- 12:20Building internal tool
- 15:32Key takeaways and next steps
- 17:58Q&A
related talks
18mChaos Engineering: Break It On Purpose
01h 04mHarnessing Chaos; the hidden ingredient behind building better systems through learning
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
34mChaos Engineering:The good, the bad & the ugly
36mChaos Engineering
27mImplementing Chaos Engr. in a Risk Averse Culture
57mChaos Engineering Primer
48mChaos Engineering: The art of breaking stuff