Micro Frontend: the microservice puzzle extended to frontend
summary
Company product Data Fabric migrates front-end into micro frontends and tests three concrete architectures: Layout (web components) (AngularJS/Angular apps wrapped in custom elements, Shadow DOM, polyfills), Galaxy (React fragments) (planned Tailor server-side fragments), and Laertes Lib (layout-as-library) (web components published on private NPM, Sashi UI design system). Laertes Lib wins: independent deploys, local testing with tiny Express mocks, faster delivery—four new apps and security/project extractions in one year—tradeoffs: hard navigations, UX drift and coordinated library-version updates.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:41Classic Study Case
- 1:26An History of Evolution
- 2:39Microservices Benefits
- 4:24Front & Microservices: The perfect match?
- 4:58Next Step of Evolution
- 5:46The Petstore Reloaded
- 7:21Micro Frontend Benefits
- 8:49Real Life Study Case: Data Fabric
- 12:27Data Fabric V2
- 13:08Design System (aka saagie-ui)
- 14:12Saagie-Layout
- 14:44What's a Web Component?
- 18:05From an Application to a Web Component
- 23:37Galaxy an aggregation of React Fragments
- 24:34Pros & Cons
- 25:53Layout-as-Lib From an Application to a Library
- 31:30Page Transitions
- 39:40Best practices, tips & tricks
- 40:39To go further
related talks
46mMicro Frontend: the microservice puzzle extended to frontend
51mMicro Frontend: the microservice puzzle extended to frontend
44mMicro Frontend: The Microservices Headache Extended to the FrontEnd
25mMicro Frontend: a microservice architecture from your frontend web apps
36mMicro Frontends in Action!
25mMicrofrontends: a Modern Approach to Complex Web Applications
57mMicro Frontends – a strive for fully verticalized systems
47mMicro Frontends Unmasked