3 ms·
* They had less than five minutes of downtime in the last twelve months, and that was considered poor. Yep, that. I did a two-year stint in a major financial n
by YeGoblynQueenne 9y ago
* They had less than five minutes of downtime in the last twelve months, and that was considered poor.
Yep, that. I did a two-year stint in a major financial network. I guess it's not a lot of time, but while I was there, there was a big outage and it was not on the mainframe side of things- some all modern server farm bought the, er, farm.
From what I can tell, at least in that company, mainframes are still in use because their stability is simply unmatched by anything in the "distributed" world; Cobol is still in use because mainframes are still in use; and nobody dares replace the Cobol code with something else, because the code itself is damn stable, as a result of hundreds of people having worked on it for several decades now- and counting.
In general, Cobol on mainframes is a rock-solid system that doesn't fall down and that nobody wants to disturb.