The good, the bad and the ugly - Component architecture at scale
summary
A Jurassic Park adoption app gets refactored: remove direct HTTP from components into services, split UI into stateful versus stateless components, and replace duplicated forms with a single component using ngContent slots. Deeply nested components cause slow change detection, so a shared BehaviorSubject service gives late subscribers the current state and flattens wiring, and a centralized store (NgRx style) holds global state when needed. Web components via Angular Elements enable platform‑agnostic, reusable output and the refactor improves maintainability and performance.
AI-written summary · about
chapters (5)
- 0:00Start
- 9:53Component based Architecture
- 11:57Dumb and Smart components
- 18:35Nested Components
- 23:43Web Components
related talks
24mThe Architecture of Components
56mModernizing Large Frontends with Web Components
23mSmart and Dumb Components
36mAngular, React, Vue and co: Harmoniously united by web components and micro apps?
34mScalable Angular Architecture
30mAngular: Keeping it Fat, Dumb, and Happy: An Architectural Approach
20mThoughtful Component Design
25mAngular Architecture: From Patterns to Implementation