I'm pretty unclear on the "how" here - but from what I can understand in the article the search resilience team injected properly tagged synthetic traffic into their system to do testing? That does seem like the kind of practice that could be part of healthy holistic approach - but the article elides a ton of details. I suppose the idea is that it promotes AWS services (with the idea of suggesting that this kind of resiliency comes easier on their platform) - but this is a great example of how good writing strips things down to the barest details. I would love to take lessons from it but I think the details actually aren't here.
Oh... "Chaos systems"=="event-driven development". For those confused about an analogy to chaos theory... as far as i can tell, there isn't one. In physics a chaos system has small perturbations that lead to an instability. I would argue this is just a large perturbation that leads to certain instabilities. I would also classify this as "network systems fault tolerance" engineering.
As a stand-alone article it is fine, and is likely to trip the more fluff than stuff alarm on many people's bs-detectors.
Who's drawing parallels with chaos theory? The origin is Netflix injecting "chaos" like taking servers down randomly. It's not tied to any scientific theory: https://en.m.wikipedia.org/wiki/Chaos_engineering
"Stress testing" might be more intuitive but that's already established as simply testing under high traffic
To add to that, I’ve read enough of my own companies blog posts to know that Y was an incorrect solution to Z, was half-implemented at best, barely improved METRIC, and has already made a lot of peoples’ lives harder for simply existing. So now I take every single one of these posts with a massive grain of salt.
