How to Organize an Angular Project
summary
Advocates splitting every feature into local libraries and mapping code by domains, using an NX monorepo to manage sharing, CI and per-folder builds; reports a real workspace with 100+ libraries, 17 applications and claims cache and CI cut full test/build wall time from 2–3 hours down to 1–2 minutes. Recommends smart vs dumb components plus adapter pattern, 80–90% unit coverage (watch for false positives), max 150 lines per file, and avoiding any except where unavoidable.
AI-written summary · about
chapters (24)
- 0:00Intro
- 1:04About Sergio
- 1:20Favorite food
- 1:57How to use Angular
- 3:46Why do I need to organize
- 4:14Improve maintenance
- 6:43Set the initial steps
- 8:00Have good requirements
- 9:41Identify domains
- 11:31Smart and dumb components
- 16:09Sustainable architectures
- 16:25Domain driving design
- 16:42Strategic and tactical design
- 17:33Angular Architects Blog
- 18:45Pick the right tools
- 20:23Quality rules
- 26:13Never use any
- 27:42Automate
- 29:09Design Patterns
- 29:34Mediator
- 29:53Service
- 30:03Facade
- 30:54Refactor Guru
- 34:25Contact Sergio
related talks
21mSustainable Angular Architecture
34mAngular Monorepo Diaries
22mSustainable Angular Architectures with Monorepos and Strategic Domain Driven Design
30mAngular in a Microservices World
31mMastering the Monorepo: How NX Schematics Transformed Our 80+ Angular Projects!
33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and Microservices
20mArchitectures for huge Angular based Enterprise Applications...
44mArchitecting large scale Angular apps with Module Federation