Angularjs 1.4 --> Angular 9 Migration Vs Bigbang Rewrite
Solution 1:
Your plan is called the "big bang rewrite", it's very common, and it's a bad idea.
In most cases, it’s the Big Bang approach that wins the argument.
But by making it a Big Bang release, you’ve maximized the chances that you’ll be behind schedule when you get to the end, and you’ve therefore maximized the chances that you won’t spend enough time preparing. This results in a bad time for both you and your customers.
Unfortunately, perhaps due to something intrinsic in human nature, this scenario is a cliche for Big Rewrite projects.
One of the keys to a successful upgrade is to do it incrementally, by running the two frameworks side by side in the same application, and porting AngularJS components to Angular one by one. This makes it possible to upgrade even large and complex applications without disrupting other business, because the work can be done collaboratively and spread over a period of time. The upgrade module in Angular has been designed to make incremental upgrading seamless.
For more information, see
Solution 2:
The goal of making every page a component is to make it easy the use of routers.
It really depends of your application, if you have a portion that is used multiple times in the same page, you can make a component with inputs and ouputs and then you can mutualise your code.
So before you create a new component you have to ask yourself two questions
Will i reuse this component in other pages ?
Does this component need to be in a specific URL?
Post a Comment for "Angularjs 1.4 --> Angular 9 Migration Vs Bigbang Rewrite"