Engineering Chaos for Resilient Applications: A Gameday Guide
summary
Walks through running a gameday using Harness Chaos Module and LitmusChaos on a demo “boutique” ecommerce app, targeting the cart deployment with a pod network packet-loss experiment under synthetic load. Observability uses Prometheus and Grafana (QPS and latency); a Prometheus probe fails while a health probe passes, dropping resilience score to 50. Shows pre/post guardrails, probe YAML (PromQL latency <50ms), Slack alerting, and a mitigation/playbook cycle for root-cause and fixes.
AI-written summary · about
chapters (14)
- 0:00Introduction to talk
- 1:06What is resilience
- 2:31Chaos engineering basics
- 4:17Game day overview
- 5:44Game day checklist elements
- 8:08Demo app setup
- 10:13Steady state hypothesis
- 12:39Choosing chaos experiments
- 14:02Guard rails and mitigation
- 15:46Harness chaos platform demo
- 18:36Running chaos experiment
- 22:51Experiment results analysis
- 26:16Experiment manifest explained
- 28:23Game day wrap-up and Q&A
related talks
01h 01mMastering Resilience Probes: Simplify chaos hypot...
30mBringing Order to Chaos: Make Your Systems More Resilient with Chaos Engineering
28mChaos Validation Made Easy
10mLightning Talk: A Culture of Resiliency through Chaos
20mKeynote: Finding the Joy in Chaos Engineering
37mBringing order to the chaos!
26mBreaking Systems for Resilience
39mPracticing Cloud-Native Resliency Is a Challenge: Decoding It with Chaos...
