StranglerApplication pattern: a legacy frontend use case
summary
Applies the StranglerApplication pattern to move a running AngularJS 1.2 single‑page app into a new codebase built with vanilla ES6 and custom elements, using webpack (and a separate Grunt build) to bundle both sides. Commits touching legacy code must be reimplemented in the new app; the migration reaches roughly 80% migrated in practice. The system runs in production during the cutover, the client keeps revenue flow, and the approach proves workable rather than rewiring everything.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:25Legacy code
- 2:08Legacy
- 2:23Client View
- 3:03Angularjs
- 3:30Angularjs as a de facto standard
- 4:04White was an experiment
- 5:38Commercial success
- 5:55Core business
- 6:13Longevity not velocity
- 7:25The legacy
- 9:44frameless approach
- 10:39the perfect solution
- 11:03writing everything from scratch
- 11:40Strangler application
- 12:18Start application
- 12:36Why angularjs
- 13:38Demo
- 19:23Be reasonable
- 20:02Quote formatting
- 20:47Framework last movement
related talks
32mThe How, What and Why of Migrating to ReactJS
19mIn the Ocean of Angular Web Applications
22mFrom Donkey to Unicorn, A new approach to AngularJS migration
05mMigrating a Portfolio of Front-End Apps to Angular
51mFrontend Monoliths: Run if you can!
49mFrom VB to Angular and Beyond Mastering Legacy Codebase Modernization
01h 07mModern Frontend Engineering
39mSustainable Client Architectures with Micro Apps