4 ms·
Sorry, I possibly stated that poorly - what I meant was: The current state of duopolistic airlines technology suppliers means that there may not be sufficient m
by Fenn 8y ago
Sorry, I possibly stated that poorly - what I meant was: The current state of duopolistic airlines technology suppliers means that there may not be sufficient motiviation to evolve the capabilities of the old systems.
Case in point: Regardless of whether Sabre/Amadeus have replaced their legacy layer with some sort of nosql, I can absolutely guarantee you that many of their primary APIs are literally screen-scraping terminal sessions and returning the screen as XML.
- tyingq 8y ago"I can absolutely guarantee you that many of their primary APIs are literally screen-scraping terminal sessions and returning the screen as XML" True, but TPF is scalable enough that it doesn't matter. The API is responsive, flexible, and handles the traffic. The ugliness isn't limiting new functionality, etc. We spend very little time talking about the cruft at the bottom. The business complexity is more important. Things like fare classes, discount codes, availability, fare basis codes, reaccommodation, and so forth. If it were all written in rust or Go + microservices it wouldn't be any more straightforward. Your product seems to confirm that. You aren't reducing that screen scraping any. But you're adding value.
- Fenn 8y agoWell said :)
- mbesto 8y ago> The current state of duopolistic airlines technology suppliers means that there may not be sufficient motiviation to evolve the capabilities of the old systems. So then what is the motivation to change this now? This seems like simple economics to me.