Microfrontends architectures
summary
OpenTable explains a working microfrontend system called OpenComponents: a runtime OpenComponents registry serves immutable components (with optional serverless back ends) to 25 microsites across ~50 engineers and >20M monthly users, letting teams publish via the oc CLI and consume with a small client library. Components support server-side and client-side rendering, per-component templates for build/render, and a Chrome extension for live testing; the stack runs in production at OpenTable and is open source.
AI-written summary · about
chapters (9)
- 0:00Introduction to challenges
- 1:44Architectural requirements
- 5:56Evaluating existing solutions
- 8:39Motivation for custom tooling
- 10:56Use cases for components
- 16:24Introducing Open Components
- 20:23Technical demo
- 30:08System internals and tools
- 34:06Pros, cons, and conclusion
related talks
38mPainless Micro Frontends Delivery
47mDeploying atomic design system at scale
57mMicro Frontends – a strive for fully verticalized systems
34mMicro Frontends
01h 13mMicrofrontends with Modules and Web Components
21mMicro-frontends: 3 years ago
25mMicrofrontends: a Modern Approach to Complex Web Applications
46mMicro Frontend: the microservice puzzle extended to frontend