I had the opportunity to play a technical lead role in the implementation of American Airlines Ticketing department microservices architecture from 2016-2023. The AA Ticketing department is responsible for the booking and payment processing of over 700K airline tickets daily. The company's IT department started its IT transformation around 2017, and the ticketing team was one of the first to have microservices in production.
The transitioning to Microservices involves significant changes not only to the technical architecture, and continuous implementation/delivery but a social and cultural organizational change. In a microservice architecture, the teams become more independent and self-organized around a specific piece of the domain. That team maintains the expertise not only on a specific business sub-domain but is also responsible for its development, deployment, and production support.
In addition to the team organization structural changes, a transition to microservices requires fundamental components that must be in place for its successful implementation. I would like to elaborate on some of these components next, and why they are essential in a microservices architecture.
Please see my next edition of "Transitioning to Microservices Architecture - Part 2" coming up. I have so much to talk about this topic since I spent significant time seeing from the ground-up in a real and practical large microservices architecture implementation in a very large enterprise.
Rubens Gomes
No comments:
Post a Comment