How to combine 20+ services into one front end without hitting turbulence

At AeroPort, we built a microfrontend architecture for a large international airport: flights, baggage, security, retail and 20+ other independent services live inside a single shell through Module Federation and Single-SPA.

What did that give us? Each service is deployed independently and does not take down its neighbors. In other words, one team can update baggage, and the flight board does not go into “oops, we didn’t touch prod” mode. For large ecosystems where releases happen more often than AI memes, this is a must.

We also improved shared dependencies: we added tree shaking, lazy loading, and vendor chunks to keep bundle size under control. Otherwise, the front end grows faster than the task list before a deadline.

The result: a unified UX, independent releases, and an architecture that does not panic when it scales.