Deep DI-ving: how Angular's DI system defeated a monolith
summary
A legacy monolith with dozens of client customizations becomes modular by relying on Angular’s hierarchical DI rather than feature branching the core claim is that injector chains let customization packages ship components and services as tokens and the team builds a chainInject helper that climbs element and environment injectors, supports wildcard name matching, infers names from route path, and exposes typed provider factories the packaging step is automated with schematics/ng add and the approach reduces merges and speeds delivery while work continues to polish types and ergonomics
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:00Small app to monolith challenge
- 8:22Customization needs and DI
- 10:31DI as solution foundation
- 14:34How Angular DI works
- 18:08Root injector limitations
- 21:19Custom injection functions
- 25:44Type safety and boilerplate
- 28:15Wildcards and context naming
- 34:42Final architecture
- 36:07Takeaways and closing
related talks
57mAngular Dependency Injection, In Depth
46mAngular Dependency Injection – Understanding hierarchical injectors
29mDI Deep Dive
17mDissecting Dependency Injection: Angular and NestJS
38mDependency Injection for Future Generations
01h 00mAngular Dependency Injection In-Depth
32mLightweight Architectures with Angular's Latest Innovations
23mDependency Injection in Nest and Angular: Intersection & Mismatch