https://www.levels.fyi/companies/alaska-airlines/salaries/so...
It's not a tech problem, it's a culture problem. Just because the infrastructure is old does not mean that it is bad. The main deciding factor is how well it is maintained. But that is to hard for many people. So much easier to say "It'S bAd bEcAuSe iT is oLd" and walk away.
At the core of most airlines is a customized version of IBM TPF, its very reliable and highly available, its all of the other stuff that breaks down.
We will in time find out what grounded AS, I wouldnt be surprised if its some sort of middleware connecting their iPads to the CRS they use for ticketing operations, but it could also be something as simple as their weight and balance application going offline.
AS is a fairly well run airline (as are DL, AA and UA) with a heterogeneous mix of systems in service, ideally this heterogeneous nature should make for a more resilient system but it also can lead to single points of failure when you have to glue too many different systems together.
It’s easy to complain about modern airlines (and I do), but it’s still true that’s never been cheaper to fly, and IT infrastructure is surely no small part of that.
AFAIK the very first large-scale commercial deployment of what we now call "distributed cloud apps" was SABRE, a ticket reservation system built back in 1960s, still in use today.
I struggle with the notion that a high quality airline operating system cannot be developed using technologies as of 2015. Most of what we are drowning in right now is the product of the last 10 years.
The last place we need fancy new shit is in air travel. This is precisely the kind of thing where you do want to call someone like IBM to install a mainframe. Failure of an airline's IT systems can begin to approach the kind of impact you get with a payment network outage.