2 ms·
There's ways to deal with stuff like that in commercial sector and academia going back a long time. It is more complex than a simple ping. It's also common to h
by nickpsecurity 10y ago
There's ways to deal with stuff like that in commercial sector and academia going back a long time. It is more complex than a simple ping. It's also common to have the protocols analyzed or even formally-verified for avoiding issues like you mentioned. Many systems will also have things like separate power supplies, certain distance apart, octocouplers, whatever to reduce hardware glitches. There's also both noise-immune (like 1802) and clockless (like Amulet) architectures to knock out those problems. Systems with a subset of these have been known to go years to over a decade without downtime.
The usual culprit in stuff like you described is management. They either force knowledgeable staff to use less to save money in short-term at long-term expense or don't even hire staff good enough for high-assurance systems. Those do cost money given they're uncommon to rare. Although, one company (Ericsson) did go all out one time making their network nine 9's just to show it could be done. Till management and customers looked at the cost. :)
EDIT to add textbook case study on management angle:
https://www.youtube.com/watch?v=nsJpTTIEySo https://www.youtube.com/watch?v=nsJpTTIEySo