Micro Frontends – a strive for fully verticalized systems
summary
Micro frontends split frontend work but buy complexity; three concrete integration strategies are compared: build-time (mono-repo bundling), server-side (Tailor/Project Mosaic fragments, Podium) and runtime (web components + vaadin-router or single-spa with lazy loading). Specific pain points: over-fetching and over-requesting from generic APIs, shared-state options (global Redux, event streams, immutable streams), index.html as the runtime environment and immutable web apps. Amazon stitches seven distinct apps across flows; mixing strategies by page or feature and avoiding offline-first PWAs with micro frontends are common recommendations.
AI-written summary · about
chapters (6)
- 0:00Start
- 17:59Hyperlink Integration breaks your SPA.
- 18:27We introduce another horizontal layer.
- 32:56A Meta Framework to handle Frameworks.
- 51:05Micro-Frontends are Distributed Systems.
- 52:00Maybe start with a monolithic first approach.
related talks
36mMicro Frontends - Breaking Monoliths
45mMicro Frontends in Action!
27mMicro Frontends: Break Up You Web App!
36mMicro Frontends in Action!
34mMicro Frontends
25mMicrofrontends: a Modern Approach to Complex Web Applications
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
29mMicro Frontends, or How to Evolve to an Extensible Frontend