Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chaos Engineering (Key ideas (Injecting a bit of failure over time is…
Chaos Engineering
Key ideas
Injecting a bit of failure over time is going to make your system more resilient in the end. Spend less time with incident management or recovery in the future.
Start with tier-2 or non-critical services first, and build up success stories to grow chaos further.
As systems become more and more distributed, there becomes a higher need for chaos engineering.
If you’re running your first experiment, get your service owners in a war room and get them to monitor the results of the test as it is running.
What are the business goals? Keep them in mind, have a proper strategy and scope chaos engineering accordingly. What is the cost of acquiring a customer? What is the impact of losing one?
-
-
Aspects
-
latency monkey: resiliency, performance, UX/customer pain
test/staging monkey: good to get started, but not good enough
-
Get started
-
inject failures between calls to the shopping cart and its immediate child calls, etc.
-
-