You Keep Using That Word, I Don’t Think It Means What You Think
summary
Built an internal app called Space Station grows from a five‑engineer sketch to ten teams touching one repo, forcing choices about isolation and deploys. Implements per‑module npm packages plus a lerna monorepo in practice, explores web components, iframes, server‑side dedicated paths and event or API state sharing (Firebase seen in the wild). Chooses a React‑only policy for contributors; the mixed approaches trade bundle size, SSR needs and runtime isolation.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:51Once upon a time in WeWork, community managers needed a managing tool
- 3:33Things started to get bigger
- 5:02At this point we have 2 options
- 15:02User should feel it's a single app
- 16:16Keep bundle size small
- 16:59Responsive as fast as possible
- 17:31No standard API
- 18:05But the concept is somehow similar
- 19:47Your mileage may vary
- 24:27Develop each module in its own separate independent repo • The main app is just wiring NPM modules packaged together
- 35:35Wait, what about communication?
- 38:33Breaking the monolith is inevitable
- 39:09You have to plan ahead to scale fast
related talks
46mMicro Frontends, Keep Using That Word, I Don’t Think It Means What You Think It Means
23mMonorepos & Spaceships - Navigating successfully through Code and Cosmos
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
49mScalable Best Practices for Your Development Team
15mApplying Microservices Design Patterns to Scale React App Development
24mManage Your Huge Codebase like a Boss
24mScaling teams with Federated Super Apps
34mAngular Monorepo Diaries