Deploying atomic design system at scale
summary
OpenTable refactors a monolithic frontend into vertically sliced microsites, adds a public registry and OpenComponents serverless components, and claims 300 deploys per week and ~100 million component deliveries per day. Components are published immutably, versioned like npm, rendered server- or client-side, previewed via a dev registry, and embedded in emails and external widgets. The system uses templates, CDNs/S3, and runtime caching and it runs in production across teams.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:20What is atomic design system
- 7:04Opentable
- 9:29Monolithic Application
- 16:06Versioning
- 20:50How we arrived
- 22:59Demo
- 28:13Component endpoint
- 30:33Publishing component
- 33:13Public registry
- 36:28Open component
- 37:08Serverside rendering
- 37:58Email
- 39:28Tools
- 40:48Summary
- 41:33QA
related talks
40mMicrofrontends architectures
38mPainless Micro Frontends Delivery
15mComponent Symphony: Composable Components for Rapid Delivery
18mAtomic Design as a Migration Strategy
11mTransforming Enterprise Frontends with Micro-Frontend Architectures
19mIn the Ocean of Angular Web Applications
19mHarnessing Microfrontends: Platforms for Web Apps
21mMicro-frontends: 3 years ago