Compositional UIs - the Microservices Last Mile
summary
Argument: composing the UI is the microservices “last mile” and it’s the hardest part because front ends reintroduce coupling if done badly. Options shown: client-side via web components shipped as NPM modules and polyfilled with Polymer; server-side via dynamic view‑model appenders or ASP.NET Core view components that render independent widgets; and pre-aggregation into a search index using ElasticSearch with immutability and change propagation (polling, CSV feeds, DB triggers/messages). Compose only where UX requires it.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:03Microservices foundations
- 5:53The composite UI problem
- 14:17Architectural approaches
- 20:20Browser-side composition
- 32:14Server-side composition
- 45:22View components
- 52:20Database-level composition
related talks
56mCompositional UIs - the Microservices Last Mile
01h 03mEvolving compositional user interfaces
51mMicrofrontends and UI Composition - a Code-First Dive
35mSSR with Micro-Frontends: How Composition Works with Modern Frameworks
34mMicroservices, but what about the UI
50mMicrofrontends: the Next Step after Microservices
57mMicro Frontends – a strive for fully verticalized systems
46mMicro Frontend: the microservice puzzle extended to frontend