Chaos Engineering / Chaos Monkey
Updated 2026-08-01
INTRODUCTION
English translation pending.
CORE DEFINITION
Formalized by Netflix, whose Chaos Monkey tool began randomly terminating production server instances. Chaos engineering treats failure as certain and asks not whether the system will break but how it behaves when it does. Experiments run in production with a defined steady-state hypothesis, a bounded blast radius and a rollback path. The qualifier is that the value comes from observation and follow-up remediation, not from the disruption itself.
SCAFFOLDING EFFECT
Reduce cognitive load
- Assumption testing: turn your belief about system resilience into a falsifiable experiment. - Weakness discovery: break things on purpose, in production, while you can still recover. - Resilience building: make controlled failure a routine practice rather than a crisis.
Anchor fast decisions
Systems fail in ways that appear only under real load and real dependencies, and those conditions are never fully reproduced in staging. Injecting small failures into production forces the real configuration to reveal its weaknesses, and it does so while the team is prepared and the damage is bounded. Each discovered weakness is then fixed, so resilience compounds instead of being assumed.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Chaos_engineeringverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS