Actually, it would've been pretty reliable if it ran on an IBM mainframe. That's their entire selling point.

There are two fundamental philosophies in fault tolerant systems. One is designing fault-tolerant hardware and running non-fault-tolerant software on it. This is what mainframes do. Practically any component of a mainframe can be hotswapped without shutting down the OS.

The other is designing fault-tolerant software and running it on non-fault-tolerant ("commodity") hardware. The latter is so popular that it's pretty much the default now, but it's not the only way of doing things.

> Actually, it would've been pretty reliable if it ran on an IBM mainframe.

How would an IBM mainframe help you with a corrupted database file? I understand that reliable hardware makes the corruption less likely to happen for hardware reasons, but it can also be the result of a software bug, or some unexpected and not correctly checked input.

You can see references to JMS, Solace, and Weblogic in various docs, like:

https://www.faa.gov/air_traffic/technology/swim/users_forum/...

https://www.faa.gov/sites/faa.gov/files/2021-10/NOTAM%20Mod%...

So probably Linux, though perhaps something else.

Could be a Solaris.

Given the vintage pedigree BSD like SunOS is an even better candidate.

Once tuned for processing they just ran - rip out a network cable and stuff it back in again, not a hiccup.

Many of the time saw no benefit in porting forward to Slow Loris.

I don't think weblogic exists for SunOS.

Correct. Java never ran on SunOS 4.x (aka Solaris 1.x), only Solaris 2.x (aka SunOS 5.x. I loved Sun's naming schemes.)

zOS for sure