3 ms·
As funny as this is, Chaos Engineering is not just random failures. It's causing known failures to see what happens. They may be a surprise to the service or ev
by jedberg 6y ago
As funny as this is, Chaos Engineering is not just random failures. It's causing known failures to see what happens. They may be a surprise to the service or even the engineers running the service, but someone should know what's happening so it can be turned off and so things can be monitored and recorded and hypotheses can be proposed and tested.
- stingraycharles 6y agoDoesn’t that kind of defeat the point of chaos engineering, that is, making the process unsupervised and triggering failure scenarios that were not yet known? I always considered the simplest form of chaos engineering to be a process that randomly kills processes on a server, and see what happens. If, on the other hand, you mean that it’s important that the “chaos” aspects needs and on/off button and that someone needs to be managing that, then I agree. :)
- jedberg 6y agoYeah, that second thing. :) The chaos itself should be random, but the time and place should not be.