Building resilient frontend architecture
summary
Company growth from 80 to 1,500 people motivates a claim: constrain to survive. Concrete techniques include reorganizing source dependencies away from the big ball of mud into layered boundaries, preferring copying or a design system over brittle app-wide shared components, and enforcing rules with forbidden dependency tests run in CI using dependency-cruiser. The promise is measurable: limited regression scope, fewer cross-team breakages, and automated prevention of forbidden imports rather than relying on dusty architecture docs.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:34Technical debt
- 8:58"Architecture" has become a dirty word
- 31:54You don't have to derive architecture from first principles
related talks
44mBuilding resilient frontend architecture
40mBuilding resilient frontend architecture
41mUsing Boundary-Driven Development to beat code complexity
27mDesigning Even Larger (JavaScript) Applications
43mScalable Best Practices for Your Development Team
50mCoevolution of Architecture & Code - Closing The Gap
42mBuilding Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership
14mGrowing pains: Scaling and re-architecting systems under fire