Upgrading Enterprise Angular Applications
summary
Explains that NG Upgrade boots an AngularJS app alongside Angular so injectors share services and components interleave, and compares two concrete migration patterns: vertical slicing (route-by-route) where one route runs one framework and duplicates components temporarily, and horizontal slicing (bottom-up) where reusable components move first increasing integration points. Gives URL strategies: single ownership with sibling outlets or mixed ownership using extract/merge, and shows lazy-load legacy bundle and pre-bootstrap to avoid shipping AngularJS until needed.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:42Agenda
- 3:03Upgrade
- 5:08Upgrade Strategy
- 7:10One Angular at a Time
- 8:06App Science
- 9:22DiSanto
- 10:19Upsides and Downsides
- 11:39Managing URL
- 12:07Single Ownership
- 14:15Mixed Ownership
- 14:48Extract and Merge
- 15:13URL Management
- 16:02Teaser
- 18:12AppScience
- 19:18Learn More
- 19:33Up Breaking Apps
related talks
23mUpgrading to Angular without ngUpgrade
24mGetting to Angular 2
41mNG-NL 2017: Pete Bacon Darwin & George Kalpakas
05mMigrating a Portfolio of Front-End Apps to Angular
26mUpgrading your AngularJS App, Without the Tears
26mThe AngularJS Migration F.A.Q.
22mFrom Donkey to Unicorn, A new approach to AngularJS migration
20mArchitectures for huge Angular based Enterprise Applications...
