Create Architecture and not Frameworks
summary
A concrete recipe: a small manifest lists JS and CSS files, the host app lazy-appends them to head and uses a react-module-container to instantiate by a global ID from a module registry, then calls angular.bootstrap (or equivalent) to mount the legacy app into a React DOM node. Lifecycle hooks forward updates (call Angular digest) and teardown destroys scopes. Result: independent, lazily loaded modules, legacy Angular or React left unchanged, independently deployable and updated by swapping manifests rather than rebuilding the host.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:51Legacy frameworks and iframes
- 6:10Ideal architecture for large apps
- 13:50Demo: Angular in React
- 21:35react-module-container library
- 28:43Isolated lazy-loaded modules
- 30:51Library code deep dive
- 34:09Where this architecture helps
related talks
20mArchitectures for huge Angular based Enterprise Applications...
39mSustainable Client Architectures with Micro Apps
31mArchitectures for huge Angular based enterprise applications npm Packages, Monorepos and Micro Apps
32mLightweight Architectures with Angular's Latest Innovations
35mArchitectures for Huge Angular Based Enterprise Applications
21mAngular based Micro frontends with module federation
40mAngular, React, Vue and Co. – peacefully united thanks to Web Components and Micro Apps
30mFederated Angular: Micro Frontends with Module Federation
