Why Invent a Framework and How to Live with It?
summary
A large React+Redux monolith (10k+ files, ~1M lines, ~12k tests) suffered from a God-object Editor API and cyclic dependencies, so the team built an internal framework called replugable that provides runtime inversion of control: a host+modules model and dependency injection by contract. They extracted features like a menu manager and quick-edit as sharable modules to reduce migration effort and make dependencies explicit, accepting trade-offs of more indirection, harder onboarding, stricter architectural coupling, and relying on tests and feature flags to keep changes safe.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:10Large codebase problems
- 7:27Editor diversity
- 11:01Modular architecture
- 14:10Choosing Replugable
- 18:20Indirect code learning
- 21:27Living with framework
- 25:30Feature deployment
- 27:17Q&A
related talks
49mFrom Frameworks to Superframeworks
31mFramework Design - Lessons Learned from Repeated Mistakes
47mEmbrace the "react fatigue"
42mIntegrating React Into Legacy Projects
35mThe Great Modularization: How We Scaled a 15-Team React Native App Without Losing
33mThe art of building a framework
28mLessons in Managing Technical Debt
28mBack to React: The Story of Two Apps