Front-end Microservices Architecture
summary
Engineers describe splitting a front-end monolith into standalone microservices delivered as JavaScript bundles loaded by a script loader and registered as custom elements. They standardize on TypeScript and shared component libraries, use routing as the single source of truth with a Redux-style event bus for messages, and implement a custom resource guard to detect/kill event leaks and CSS bleed; one service is in production, two in development, a third planned, and strict lifecycle/versioning controls are required.
AI-written summary · about
chapters (12)
- 0:00Frontend microservices intro
- 3:58Monolith to microservices
- 8:33Shell wrapper
- 11:22Microservice theory
- 18:37Integration problems
- 23:13Deploying and testing
- 27:13Q&A
- 30:31Parallel work limits
- 31:53Code organization
- 33:18Testing constraints
- 34:21Security against scripting
- 35:02Conclusion
related talks
44mMicro Frontend: the microservice puzzle extended to frontend
44mMicro Frontend: The Microservices Headache Extended to the FrontEnd
37mIntroduction to Micro Frontends
36mMicro Frontends - Breaking Monoliths
46mMicro Frontend: the microservice puzzle extended to frontend
39mScaling Frontend Development
57mMicro Frontends – a strive for fully verticalized systems
51mMicro Frontend: the microservice puzzle extended to frontend
