How a micro-frontend approach works on a large scale web application
summary
Argues that frontends can adopt microservice patterns and gives two concrete mappings: split by page or component teams (header/footer as standalone apps) or by end-to-end feature teams owning DB-to-UI. Requires technology agnostic stacks and isolated runtime with each micro-frontend having its own build/test/deploy pipeline. Benefits are independent upgrades, simpler testing and smaller scope for changes; measurable costs are duplicated JS bundles (multiple React copies hurting performance) and integration bugs when composing into the container, so frequent integration is mandatory.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:33Defining Micro Frontends
- 1:28Evolution of Front End
- 3:50Approaches to Implementation
- 5:59Key Characteristics
- 8:33Benefits of Micro Frontends
- 9:47Challenges and Risks
related talks
50mMicrofrontends: the Next Step after Microservices
29mMicro Frontends, how to evolve to an extensible frontend
29mMicro Frontends, or How to Evolve to an Extensible Frontend
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
57mMicro Frontends – a strive for fully verticalized systems
44mMicro Frontend: The Microservices Headache Extended to the FrontEnd
33mMicro Frontend Architecture
34mMicro Frontends