If your goal is for your server to be urine-proof, then peeing on it from time to time to make sure would be a good idea.

sadly my analogy failed most peoples IQ :facepalm:

Yes, we're all too dumb to understand your brilliance. Couldn't possibly be the fault of your analogy.

no that would be you.

Point I was making is that pulling out process's/servers/cables is all fine (aka pissing on your server) but it is not a ideal way to test. It is better IMHO to test out on what you could call weak hardware, as in realy throttled CPU/disc/network etc and see were things break as these emulate what potentual peak bottlenecks you will get. This approach is better as you get to test out a single process system as apposed to only being able to test cloud based approaches as this does.

Pulling out processes/servers/cables is an ideal way to test what happens when you pull out processes/servers/cables. Especially when you want to see how it affects a system that is too large to realistically reproduce in a test rig (though presumably you would still want to run it in your scaled down test rig too).

Throttling CPU/disc/network is all well and fine and necessary too, but that's only one set of failure scenarios, and won't protect you against a whole range of failures related to systems just disappearing as they crash, or failing to restart, or any number of other concerns.

Chaos monkey isn't for testing peak bottlenecks, it's for testing random failures at the per instance level. For bottleneck testing I expect Netflix has another tool with a similarly simian name, but that's not the topic of discussion.