Painless Micro Frontends Delivery
summary
OpenComponents provides a runtime registry with versioned endpoints where each frontend component is a separately published package; a CLI builds and uploads assets to a CDN, templates let teams use different frameworks, and components support both client and server rendering. Each component can include a server-side function shipped with component so private APIs travel with a specific version. A Chrome tool previews and hot-swaps component versions, enabling independently deployable UI pieces at OpenTable scale.
AI-written summary · about
chapters (9)
- 0:00Introduction to Open Table
- 1:56Why use micro front-ends
- 6:55Technical implementation
- 9:36The Open Components registry
- 12:24Client and server interaction
- 14:18Architectural evolution
- 18:53Live demo of components
- 29:15Integration and tooling
- 34:37Q&A and concluding remarks
related talks
40mMicrofrontends architectures
46mMicro Frontend: the microservice puzzle extended to frontend
57mMicro Frontends – a strive for fully verticalized systems
47mDeploying atomic design system at scale
46mScaling Micro-Frontends with Custom Elements
34mMicro Frontends
25mMicrofrontends: a Modern Approach to Complex Web Applications
51mMicrofrontends and UI Composition - a Code-First Dive