If we take an enterprise angular 2 web app it has several modules(screens) such as Customer management, Reservations, Booking management, Reporting and etc....
What we normally do is we create common components in a component library and use them on main angular application. The main angular app contains all the modules(screens) with REST API integrations(assuming backed is REST). When app is getting bigger & bigger compile time and rendering consuming more time & resources. Also if one particular area is having a issue we cannot have a release since all are bundle to one app.
As you all know Micro service architecture is a method of developing software systems that has grown in popularity. So, my question is can we apply same architecture for these type of enterprise angular 2 apps?.
It is like this. We have a customer management as a separate angular app. Again Booking management is another angular app. Reporting is another app. These apps are going to be separate war files when deploying to the web server.
Once we have developed such loosely coupled apps this will reduce the over head of project size, compile time & resources. Also this will make unit testing more easier. Particular set of developers are only considering the only one unit of the module.
Kindly share your expert thoughts about this
Thanks.