Micro Frontends: The Good, the Bad, and the Ugly
summary
A greenfield online shop is rebuilt using micro-frontends deployed to separate URLs with Vue.js and the Vue Server Renderer Plugin, UI pieces as web components, and first-party libraries in TypeScript. The talk examines how cross-team isolation reduced coupling but introduced deployment and runtime complexity, discusses iframe and other integration patterns and server-side rendering trade-offs, and reports surprising issues such as persistent memory leaks across micro-frontends and brittle semantic-versioning that forced rollbacks and coordination.
AI-written summary · about
chapters (13)
- 0:00Micro Frontends intro
- 2:01Choosing Micro Frontends
- 4:11E-commerce checkout
- 6:15Real-world lessons
- 9:31Trade-offs in architecture
- 12:26Custom vs frameworks
- 15:45Layout service
- 18:36Client-side communication
- 21:24Functional requirements
- 24:19Maintenance and scalability
- 26:47Config and deployment
- 29:17Debugging incidents
- 30:21Summary
related talks
34mMicro Frontends
57mMicro Frontends – a strive for fully verticalized systems
56mMicro Frontends with Vue.js
29mMicro Frontends, or How to Evolve to an Extensible Frontend
46mMicro Frontend: the microservice puzzle extended to frontend
45mMicro Frontends in Action!
25mMicrofrontends: a Modern Approach to Complex Web Applications
52mMicro frontends: prepare for the ride
