Chaos Engineering Community Tales and Future
summary
Compares concrete signals: adoption numbers like 5000 GitHub stars for litmus and 9,000+ Slack members, recent commit activity such as ~100 commits to Chaos Mesh in 12 months, and which tools run where (Gremlin, litmus, Chaos Toolkit, Chaos Blade, AWS FIS, Azure Chaos Studio, Kraken). Describes built outcomes — dashboards, blast‑radius controls, CI/CD experiments — and argues collaboration patterns, contributor shortfalls, and enterprise vs open‑source tradeoffs so a viewer can judge practical value.
AI-written summary · about
chapters (8)
- 0:00Introduction and Speaker Background
- 0:59Agenda Overview
- 1:40Chaos Engineering in Practice
- 2:51Evolution of Chaos Engineering
- 3:39Open Source and Enterprise Solutions
- 12:59Community Growth and Contributions
- 25:43Challenges and Future of Chaos Engineering
- 33:13Conclusion and Final Thoughts
related talks
05mProject Lightning Talk: Chaos Unleashed: LitmusChaos and Its Journey Towards CNCF Graduation
34mChaos Engineering For Hybrid Targets With LitmusChaos
28mChaos Engineering alongside Litmus and Jenkins
52mPanel Discussion
29mThe Psychology of Chaos Engineering
21mLightning Talk: LitmusChaos Project Updates
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
26mBreaking Systems for Resilience