Building resilient frontend architecture
summary
Argues that resilient frontends come from concrete constraints not vague patterns, claims directional source-code dependencies stop the “big ball of mud,” and shows automation that enforces them: forbidden dependency test run in CI using dependency-cruiser. Recommends being conservative about reuse—prefer a design system or copy and paste—and shows layered apps isolate change. Gives evidence from a company that grows from 80 to 1,500 people, describes implemented checks and outcomes, and reports the enforcement approach actually reduces cross-team regressions.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:08Recurring technical debt
- 13:12Enabling constraints in
- 24:04Impact of time on shared code
- 30:00Forbidden dependency tests
related talks
44mBuilding resilient frontend architecture
33mBuilding resilient frontend architecture
38mMicro frontends anti patterns
44mDependencies; Devil or Darling?
27mDesigning Even Larger (JavaScript) Applications
41mUsing Boundary-Driven Development to beat code complexity
29mDesigning very large JavaScript applications
51mA Contrarian View of Software Architecture