“Micro Frontends”- You Keep Using That Word...
summary
Explains what people mean by “micro frontends” and maps specific problems of large frontend apps to different micro-frontend solutions. Covers scenarios such as running multiple UI frameworks in one application and enabling teams to own separate parts of the codebase, and compares how those approaches address scale and team independence.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:20Once upon a time in WeWork, community managers needed a managing tool
- 8:51User should feel it's a single app
- 9:23Keep Bundle size small
- 10:22No standard API
- 13:48Your mileage may vary
- 28:09Wait, what about communication?
- 29:22Event based communication
related talks
36mMicro frontends - A Microservices Approach to the Front End
44mMicro Frontend: The Microservices Headache Extended to the FrontEnd
36mMicrofrontends: Scalability Savior or Unmanageable Maze?
29mMicro Frontends, how to evolve to an extensible frontend
29mMicro Frontends, or How to Evolve to an Extensible Frontend
50mMicrofrontends: the Next Step after Microservices
34mMicro Frontends
57mMicro Frontends – a strive for fully verticalized systems