The coupling problem in micro frontends
The micro frontend pattern promises team independence: each team owns a vertical slice of the UI and deploys it independently. In practice, this independence is undermined by shared client-side state.
If MFE A and MFE B both need to know the current user cart, they must either share a state store (coupling) or duplicate state (staleness). Cross-MFE event buses, shared stores, and global state contracts emerge as the coordination mechanism. The teams are not independent; they are coupled through the state bus.
SAUI eliminates the coupling
Under SAUI, there is no client-side state to share. Each MFE consumes its own projection from the server. The server is the source of truth. MFEs do not need to communicate with each other because they each have a direct line to the authoritative state.
If MFE A updates cart state by submitting an AddToCart action, the server appends the event and updates the cart projection. MFE B next render (or SSE update) reflects the current cart. No event bus. No shared store. No cross-MFE contract.
Team isolation in practice
- Each team owns a projection: their read model from the server
- Each team owns their actions: their write interface to the gateway
- Teams deploy independently: no shared build output
- Teams test independently: no cross-MFE integration test surface
The seam between teams is the projection contract and the action API, both of which are server-defined. Changes to one team UI do not affect other teams. Changes to one team projection require coordination with the backend, but not with other frontend teams.
Composition
MFEs under SAUI are composed server-side: each team template fragment is included in the page layout by the server. There is no client-side module federation, no runtime JS composition, no shared bundle negotiation.
Each fragment is a server-rendered HTML partial, served by the team own backend, composed into the page at the BFF or reverse proxy layer. The client receives assembled HTML. This is simpler, faster, and more resilient than client-side composition.