Compositional UIs - the Microservices Last Mile
summary
Argues that the “last mile” of microservices is the UI and gives concrete composition patterns: compose in the browser with webpack/NPM components for independent widgets; compose on the server using model-side aggregators or ASP.NET Core view components with resilient calls (use Poly for resiliency); or prebuild a tailored read model via Elasticsearch denormalizers fed by API pulls, file drops or messaging. Advises minimal composition, larger capability-oriented boundaries, and defensive handling of latency and failures.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:55What is a Microservice
- 3:08Autonomy
- 4:39Microservices
- 6:08Conways Law
- 7:07Service Boundaries
- 7:57Integration Books
- 8:27Compositional UIs
- 9:20Selfridges
- 11:57Last Mile Problem
- 12:40The Most Important Part
- 13:09Single coherent user interface
- 13:48Composite applications
- 15:21The user experience
- 19:02Frontend technology
- 24:19Boundaries
- 27:01Serverside Composition
- 28:24Invisible Product Details
- 31:09Resiliency
- 36:59View Components
- 42:24Search
- 46:09Data Duplication
- 48:59Backend Integration
related talks
01h 02mCompositional 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
50mMicrofrontends: the Next Step after Microservices
25mTES Microservices
34mMicroservices, but what about the UI
26mThe art of visualization and composition in building component systems
