Architectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and Microservices
summary
Claims concrete tradeoffs and concrete tools: Angular CLI v6 actually generates libraries that build for NPM publish and support AOT and tree‑shaking; a monorepo shares one node_modules and uses Nx to visualize dependency graphs and enforce linted access rules; micro apps use hyperlinks, iframes, or bootstrapped multiple SPAs with lazy loading and web components for UI composition. Versioning and publish friction hurt npm packages, coordination and rigid contracts hurt monorepos, and duplicated bundles plus state transfer hurt micro apps — decision tree maps which option fits which need.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:22Contents
- 1:51About me...
- 2:54Why Packages?
- 3:22Create npm-Packages with CLI = 6
- 11:02Moving back and forth
- 12:21Tooling & Generator
- 16:35Idea
- 18:42UI Composition w/ Hyperlinks
- 22:30Providing a (SPA based) Shell
- 27:23Disadvantages ;-
- 28:39Some General Advice
- 31:29Blog SOFTWAREarchitekt.at
- 31:52Conclusion
related talks
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
35mArchitectures for Huge Angular Based Enterprise Applications
20mArchitectures for huge Angular based Enterprise Applications...
30mAngular in a Microservices World
34mAngular Monorepo Diaries
22mSustainable Angular Architectures with Monorepos and Strategic Domain Driven Design
45mA Software Architect's Approach towards SPA Based Micro Apps
28mAngular in a microservices world
