From experimentation to continuous verification
summary
Defines chaos engineering as formalizing resilience not breaking things and shows Datadog building a usable chaos platform that ties Gremlins/Litmus/Chaos Mesh/Harness and internal fault injectors into three teams: fault injection, SDLC integration and enablement. Runs large scale game days (200 engineers for 8 hours, ~150 test cases) for three years, uses fake observability to replay incidents, integrates continuous verification into CI/CD with monitor gates that auto‑rollback, and offers autogenerated dependency failures and property‑based tests so teams can validate predicates without deep chaos expertise.
AI-written summary · about
chapters (11)
- 0:00Introduction to Chaos Engineering
- 0:24Defining Chaos Engineering
- 1:41Challenges in Adopting Chaos Engineering
- 2:10Speaker Introduction and Background
- 2:39Historical Context of Chaos Engineering
- 3:39Chaos Engineering Practices and Scenarios
- 5:09Formalizing Resilience and Incident Management
- 8:35Continuous Testing and Implementation
- 11:20Datadog's Approach to Chaos Engineering
- 17:01Human Factors in Chaos Engineering
- 20:18Conclusion and Q&A
related talks
27mChaos Engineering: The Path to Reliability
48mChaos Engineering: The Path to Reliability
18mChaos Engineering: Break It On Purpose
26mBreaking Systems for Resilience
32mTrajectory of Chaos
23mBring Chaos to Your Org
38mWhy software developers should build a resilience culture based on chaos engineering
29mImprove Resilience with automated chaos engineering