I'm a Frontend Engineer @ extrategy. I'm also speaker at tech conferences and reviewer for Manning, Packt and Pragmatic Programmer. I like to relax playing with my Playstation or cooking some strange ethnic dish for me and my girlfriend
A legacy frontend use case
What Makes a Codebase "Legacy"?
Fear to modify the code
"European CV or letter of recommendation?"
Legacy Code is Valuable
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
Our client needed Velocity
So we chose the framework that we knew better
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
Let's Change Framework!
What Framework should we use?
Rewriting everything from scratch?
Our client is actually making money from the software
What did we learn?
Don't be rational; be reasonable.
...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
Tech Decisions based on business needs
How's it going?
One Simple Rule
Never Commit on the old application
StranglerApplication Pattern: A legacy frontend use case - IJS Munich 2018
By Francesco Strazzullo