A recent flight booking revealed an astonishing technical reality: the reservation infrastructure handling billions of passengers annually dates back to the 1960s. This legacy system, born from American Airlines' need to replace index cards, runs on an operating system predating Unix. The initial concept, sketched between an airline president and an IBM salesman mid-flight, became the foundational Global Distribution System (GDS).

That core technology is Transaction Processing Facility (TPF), an IBM mainframe OS designed for massive, simple transactions with sub-millisecond latency. Unlike modern systems relying on processes and heaps, TPF uses short-lived programs against fixed memory cells, resulting in extreme throughput nearing 50,000 TPS during peak sales events. Airlines stuck with it because replacement systems couldn't match its raw performance metrics.

Major GDS players like SABRE and Amadeus built upon this foundation, maintaining core command languages and data models even after migrating to other hardware. While modern Passenger Service Systems like Amadeus Altéa interface with this backbone, the underlying protocols persist. Even budget carriers like IndiGo use specialized systems like Navitaire, trading interoperability for operational simplicity.

This architectural persistence, codified before widespread modern computing concepts solidified, demonstrates a rare case where a purpose-built runtime beat decades of architectural evolution. The consistency of the TPF runtime, even across different GDS platforms, is what allows complex multi-airline bookings to function reliably today.