Comment by dijksterhuis

while we can learn from the past, we probably shouldn't look at it through sunglasses that are rose-tinted ;)

---

sabre, the company that owns and builds the current version of the system SABRE used by major companies today, uses all of those things the parent and you mentioned

> Google Cloud-native infrastructure that is scalable and secure. Microservice-enabled architecture that supports modularity. API-first approach for an open platform. [0]

> We rebuilt Sabre from the ground up: cloud-native technology, AI baked into the foundation, one goal in mind. Your success. [1]

yeah ... it's 'ai powered' now.

[0]: https://www.sabre.com/resources/viewpoints/offer-order-strat... (skip to the 'different by design' heading)

[1]: https://www.sabre.com/about/

---

> Do we really need to stack all these turtles (abstractions) just to get instructions to a CPU?

no. but those abstractions are there for things like scaling, reliability, redundancy, flexibility, ... and a bunch of other things not related to solely getting some instructions to a CPU. the number of turtles has increased because customers have more requirements for software today than they used to have in the 1960s.

sometimes we need the simplest solution with fewest dependencies. sometimes we need lots of turtles... it really depends on the problem in front of us.