Angular in a microservices world
summary
Claim: front ends move from per-team apps to shareable feature libraries inside an Nx monorepo so all code uses one Angular version and avoids duplicate API clients. Demonstrated tools and practices: TypeScript path mappings for library imports, TS lint rules to forbid deep imports and enforce allowed dependencies, and automatic dependency graph analysis to run CI only on impacted apps and libs. Evidence: real client adoption that reduced duplicate code and kept CI efficient, with caveats around coordinating upgrades and org buy-in.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:16Applications that we build today - deployment overview
- 6:04Applications that we build today - Team Repo overview
- 13:29Creating the example frontend
- 16:01Creating the links
- 16:57Path mappings
- 18:05Public API
- 19:29Define allowed relationships
- 19:42Configuring tags - nx.json
- 19:58Defining allowed relationships
related talks
21mSustainable Angular Architecture
35mArchitectures for Huge Angular Based Enterprise Applications
22mSustainable Angular Architectures with Monorepos and Strategic Domain Driven Design
33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and Microservices
34mAngular Monorepo Diaries
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
20mArchitectures for huge Angular based Enterprise Applications...
32mAdventures in Angular
