I can't tell if the article is describing how complex systems fail or if they are using failure characteristics to define complex systems.
How Complex Systems Fail (1998)
11–20 of 90 posts
Re: How Complex Systems Fail (1998)
#12> Failure free operations require experience with failure. This is why we created Chaos Engineering. By constantly forcing failure, it made us always create systems in defense of that failure, and gave us great data on where the tipping point is for different systems within a particular failure mode.
Re: How Complex Systems Fail (1998)
#13Re: How Complex Systems Fail (1998)
#14Re: How Complex Systems Fail (1998)
#15https://en.wikipedia.org/wiki/Normal_Accidents
https://en.wikipedia.org/wiki/Meltdown_(Clearfield_and_Tilcs...
Re: How Complex Systems Fail (1998)
#16The most commonly cited subtext or thrust of it is that "root cause analysis", at least on complex systems, is a fools errand. Something goes wrong, say, in a distributed lock system, and your whole deployment system enters a metastable failure state. Naturally, the "root cause" seems like lock system resiliency. But definitionally a metastable failure is one that persists after the inciting condition is resolved. Now you have two "root causes", the lock failure and the metastability of the deployment system fault. Keep looking and you'll find more.
But to me the biggest brick to the forehead in this piece is further observation that random things are failing all the time in any complex system. "Complex systems run in degraded mode". Resilient components are good, but it's the resiliency of the overall process that orchestrates the whole system that determines whether things are going to blow up.
All practitioner actions are gambles. I should have that inked somewhere.
Re: How Complex Systems Fail (1998)
#17All of this sounds just like any air crash investigation I ever read
Re: How Complex Systems Fail (1998)
#18> Failure free operations require experience with failure. This is why we created Chaos Engineering. By constantly forcing failure, it made us always create systems in defense of that failure, and gave us great data on where the tipping point is for different systems within a particular failure mode.
PS. Btw, I am certain that this is the main cause of the mental health crisis amongst young people.
Re: How Complex Systems Fail (1998)
#19I'm a broken record on how important I think this document is, and that it's hard to appreciate it until you've had extended experience with complex systems actually failing. The most commonly cited subtext or thrust of it is that "root cause analysis", at least on complex systems, is a fools errand. Something goes wrong, say, in a distributed lock system, and your whole deployment system enters a metastable failure…
If you want a bit of cheese to go with that wine, this article pairs nicely with The Grug-Brained Developer: https://grugbrain.dev/