Slide 6
Slide 6 text
Chaos Engineering Principles
Define "Stable" and "Robust"
Error rates, throughputs, latency percentiles, response time percentiles,
consumer groups, etc.
“Real World” Events and Parameters
Unexpected request payloads, network incidents, traffic peaks/bottoms, etc.
Don't ignore environmental differences
Chaos strongly prefers to experiment directly on production traffic. Run
experiments on jungle.
Automate failure for autonomous recovery
Chaos certainly prefers to experiment unexpected behaviors at unexpected times.
Run experiments automatically.
Don't turn a blind eye to customer impact
Some short-time negative impacts may be acceptable depending on business but,
these should be minimized.