Chaos Engineering: Unleash the Monkeys
summary
A demo Pizza webshop runs on Kubernetes with a frontend, GraphQL API, RabbitMQ and .NET microservices; chaos tools inject faults via a .NET library (Simi) and config toggles in Azure App Configuration. Experiments kill the products DB, add retries plus a cache and a circuit breaker (breaks after 6 exceptions for 30s) and move ordering to a queue so orders still process. Injection uses 30% faults and added latency (300–550ms); result: ordering survives, cross‑sell is degraded but noncritical.
AI-written summary · about
chapters (13)
- 0:00Chaos engineering intro
- 1:04What chaos engineering is
- 12:04Why chaos engineering matters
- 15:13Start with chaos engineering
- 24:50Demo setup
- 26:17Kill product DB experiment
- 34:05Resilience with cache & circuit breaker
- 36:35Cross-selling service test
- 41:00Ordering functionality check
- 46:27Chaos simulation .NET packages
- 55:47Recap of experiments
- 56:53Key takeaways & next steps
- 1:00:03Closing & Q&A
related talks
37mBringing order to the chaos!
57mChaos Engineering Primer
49mChaos Engineering: Withstanding Turbulent Conditions in Production
35mChaos Engineering – from destructive monkeys ...
33mBeyond the Monkeys Chaos Engineering on the Cloud
37mChaos Engineering: The Fine Art of Breaking Stuff in Production on Purpose
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
01h 01mEmbrace chaos to achieve stability