Architectures for Huge Angular Based Enterprise Applications

on YouTube ↗35m

" summary

Three concrete options and when they work: publish reusable code as NPM packages built with CLI 6 (gives versioned libraries but causes publish/test role switching and version conflicts), keep everything in a mono repo using Nx so one shared node_modules avoids mismatched Angular/RxJS versions and enforces dependency rules, or split into micro apps via one index.html bootstrapping multiple SPAs (or hyperlinks/iframes) to allow independent deploys at the cost of duplicate bundles and UI-consistency effort; use the decision tree: shared state, legacy isolation, and independent deploys.

AI-written summary · about

" chapters (11)

1. 0:00Start
2. 2:33Why Packages?
3. 3:04Create npm-Packages with CLI - 6
4. 10:19Moving back and forth
5. 11:32Tooling & Generator
6. 18:31UI Composition w/ Hyperlinks
7. 21:33Providing a (SPA based) Shell
8. 27:33Disadvantages ;-
9. 29:43Some General Advice
10. 33:43Conclusion
11. 34:51Contact and Downloads

" related talks

• 20mArchitectures for huge Angular based Enterprise Applications...Manfred Steyer · NG Poland 2018
• 33mArchitectures for huge Angular based Enterprise Applications: npm Packages, Monorepos and MicroservicesManfred Steyer · DevOne 2019
• 31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro AppsManfred Steyer · Angular Connect 2018
• 45mA Software Architect's Approach towards SPA Based Micro AppsManfred Steyer · Voxxed Days Microservices 2018
• 01h 00mUsing Monorepos for Scalable AppsJames Henry, Dylan Johnson, Mike Haas · ng-conf 2019
• 28mAngular in a microservices worldKwinten Pisman · ngVikings 2019
• 39mSustainable Client Architectures with Micro AppsManfred Steyer · FrontEnd Con 2018
• 21mSustainable Angular ArchitectureManfred Steyer · EnterpriseNG 2020