Making Sense of Chaos: Implementing Chaos Engineering in a Fintech...
summary
GoTo Financial implements chaos engineering to verify SLOs under heavy regulation, running controlled experiments against production-like systems and piggybacking them on routine ops. They build hypotheses from postmortems, schedule experiments with a Chaos controller+orchestrator, and capture metrics/history in a central store. Experiments reveal surprising findings — hidden ordering dependencies and restart sequences — and drive fixes that move failure modes left. The program balances SLO compliance, postmortem-driven experiments, and continuous verification to improve confidence in a complex payments platform.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 3:57Complexity in fintech systems
- 6:05Compliance and reliability challenges
- 10:45Journey to chaos engineering
- 15:24Breaking down problems systematically
- 18:17Post-mortem analysis and learning
- 21:13Continuous verification practices
- 23:17Tools for chaos engineering
- 26:18Sustainable reliability in regulated industries
- 28:29Q&A and acknowledgments
related talks
25mChaos Engineering Applied To the FinTech Domain
27mExecuting Chaos Engineering in Production at a Critical Financial Institution
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
15mChaos - Does It Need to Be Included in Test Strategy?
19mLearnings from Chaos experiments
37mUse Chaos Testing to Build Resilience in the Software
54mControlled Chaos: The Inevitable Marriage of DevOps & Security
40mSecurity & Chaos Engineering: Resilient Distributed Systems