StranglerApplication Pattern
A legacy frontend use case
(a talk with a lot of GIFs)
Ego Slide
f.strazzullo@extrategy.net
@TheStrazz86
https://github.com/francesco-strazzullo
https://medium.com/@TheStrazz86
https://slides.com/francescostrazzullo
What Makes a Codebase "Legacy"?
Fear to modify the code
"European CV or letter of recommendation?"
Code is legacy when is not easily adaptable to new business needs
Let me tell you a story...
In 2013 we started a new greenfield project
The porting of a desktop business-management software to a SPA
And we chose AngularJS
It was a good choice
It was a de facto standard
It was an experimental business
Quick feedback
Our client needed Velocity
The software is now a commercial success
It's the core business of our client
Now Velocity is not our top priority...
Now what our client needs is Longevity
Legacy Anyone?
What Framework should we use?
Frameworkless
How?
Rewriting everything from scratch?
StranglerApplication
What did we learn?
Don't be rational; be reasonable.
Gerald Weinberg
...when designing a new application you should design it in such a way as to make it easier for it to be strangled in the future
Martin Fowler
Tech Decisions based upon Business
How's it going?
Thanks!