Architectures for huge Angular based Enterprise Applications...

on YouTube ↗20m

" summary

Three concrete patterns with tradeoffs and a decision tree: split code into npm packages (Angular CLI libraries, publish to a registry, versioning and publish overhead), or one mono repo (single node_modules to avoid version conflicts but harder independent evolution), or micro apps (shell or hyperlinks that lazy-load independent Angular SPAs, iframes for legacy, web components for widgets). Demonstration shows a shell bootstrapping multiple Angular apps on demand; criteria are shared state, legacy integration, and need for independent deployment.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 1:47Using Npm Packages
3. 2:04Npm Packages
4. 5:35The Mono Repo Approach
5. 7:13Creating a New Library
6. 10:54The Micro Apps Approach
7. 15:50Web Components To Reuse Widgets
8. 19:04Conclusion

" related talks

• 35mArchitectures for Huge Angular Based Enterprise ApplicationsManfred Steyer · AngularNL 2019
• 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
• 39mSustainable Client Architectures with Micro AppsManfred Steyer · FrontEnd Con 2018
• 30mAngular in a Microservices WorldKwinten Pisman · NG-BE 2018
• 41mSuper scalable and robust architecture definitions for Angular at an EnterpriseNatalia Venditto · Voxxed Days Frontend Bucharest 2019
• 21mAngular For EnterpriseStephen Fluin · ng-conf 2019