My dashboardSign in

Design patterns and architecture · One page, many teams

Micro-frontends-style app

Illustrative system design for a one page, many teams app like Micro-frontends: 3 topics to read, from requirements to deep dives.

Illustrative design, not Micro-frontends’s actual implementation. Arrowbox is not affiliated with Micro-frontends’s owner. Disclaimer

Start with Splitting by team Sign in to start readingUpdated 2 Oct 2026

Core

  • When to split a frontend, and along which seamsIntermediate · 25 min read · Sign in to read

    Micro-frontends fix an organisational problem, many teams blocked on one release. Cut by business domain so each team owns whole pages or whole fragments, end to end.

  • Putting the pieces together: build time, server, edge and browserAdvanced · 36 min read · Sign in to read

    Fragments can be assembled when the app is built, on the server or edge per request, or in the browser at runtime. The later you assemble, the more independent the teams and the more you pay at load time.

  • Contracts between micro-frontendsAdvanced · 35 min read · Sign in to read

    Independent parts stay independent only if they talk through narrow, versioned contracts (URL, attributes, events) and never reach into each other's state, styles or globals.