Building resilient frontend architecture
summary
Claims that resilient frontends come from simple, enforced constraints: use directional dependencies to shrink regression scope, prefer local duplication over brittle shared widgets unless extracted into a proper design system, and enforce boundaries with CI checks such as dependency-cruiser and dependency tests. Notes a real case from a company growing 80→1500 people, recommends automating checks, and explores monitoring as fitness functions (build time, dependency counts) to keep architecture working rather than drifting.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:50Rewriting code
- 16:41Source code dependencies
- 21:13Sharing components
- 22:09Dry code
- 24:13Reusable code
- 27:10Dependency tests
- 31:31Architecture on the small
- 34:30The human element
- 36:32Automating code reviews
- 39:17Eliminating dependencies
- 40:37Thirdparty libraries
- 41:51Questions
related talks
40mBuilding resilient frontend architecture
33mBuilding resilient frontend architecture
38mMicro frontends anti patterns
27mScaling Your Front-End in a Realistic Way!
18mBeyond the Hype: Facing Micro Frontend Challenges in Large-Scale
52mMicro frontends: prepare for the ride
11mMicro-Frontends Anti-Patterns
49mSOLID Frontend Architecture. Do we need it? Yes!