Back to Catalog
Microservices
UI Patterns
Server-Side Page Fragment Composition
Each team generates their HTML slice server-side — a compositor stitches fragments into a full page.
Intent & Description
Real-world Use Case
Product page compositor calls /fragments/product-details, /fragments/reviews, /fragments/recommendations. Each returned by the owning team’s service. Compositor assembles and returns one HTML page. Browser gets a complete, SEO-friendly page.
Source
📌 TL;DR
Server-side micro-frontends — teams own their HTML fragments, compositor stitches the page. SEO-friendly, team-autonomous, assembler-complex.
Advantages
- Server-rendered = SEO friendly, fast first paint
- Team ownership extends to full UI stack
- Fragment caching at CDN = scalable
- No JS required for initial render
Disadvantages
- Compositor is a bottleneck — must aggregate N requests server-side
- Page assembly latency = slowest fragment (mitigate with timeouts + fallbacks)
- Consistent design system still needed across team-owned fragments
- More complex than a single server-rendered app