Chaos Engineering Applied To the FinTech Domain
Talkat KubeCon + CloudNativeCon North America 2022 · on Wednesday, 2022-10-26· at 11:55· Virtual Platform Only·
summary
FIS applies LitmusChaos with Dynatrace/Prometheus, Jenkins CI/CD and load generators to run declarative CRD/operator-based experiments such as pod HTTP latency, memory-saturation and pod-kill, measuring response time, throughput, error rate, CPU, memory and connection-pool usage. A documented case shows expected error impact of ~2% becoming ~30%, and Captain automates pre/during/post evaluations and returns pass/fail so chaos runs per release across hundreds of products, exposing toil and quantifying resiliency.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:49FinTech Problem Statement and Solution
- 2:25FinTech Technical Architecture
- 4:42Chaos Engineering - Definition and Practice
- 6:11Chaos Engineering Eco-System
- 18:16Litmus Chaos Experiments
- 20:33Chaos Evaluation - An Example
- 24:20Chaos Engineering - Stakeholder Value
related talks
29mMaking Sense of Chaos: Implementing Chaos Engineering in a Fintech...
27mExecuting Chaos Engineering in Production at a Critical Financial Institution
40mSecurity & Chaos Engineering: Resilient Distributed Systems
38mCreating chaos in containers
32mAre you hesitant to run chaos experiment...
43mCyber Chaos Engineering
54mControlled Chaos: The Inevitable Marriage of DevOps & Security
37mUse Chaos Testing to Build Resilience in the Software
