I read through the literature that AngularJS is made for single page .
And if I use the same for a larger application, with several screens. What would be the negative impacts of using AngularJS? And if I wanted these impacts not to be generated, but to continue using AngularJS, could I think of a microservices architecture?
AngularJs is made for single page, right?
Yes, Angular is a framework for single-page applications - which means your operating model prevents full reloads (such as navigating to another page, for example, where the browser discards the current page and loads all the resources indicated in the new page).
And if I use the same for a larger application, with several screens. What would be the negative impacts of using AngularJS?
None - or rather, it depends on the implementation model. In the same way that sub-optimized solutions in traditional HTML exist (for example using several IFRAMEs), an Angular solution can also be malformed.
The equivalent mechanism, in the angular world, to the flow of navigation between pages / modules is known as routes .
And if I wanted these impacts not to be generated, but to continue using AngularJS, could I think of a microservices architecture?
The two are not related. The most common problems in implementations Angular has to do with flow and load of resources. Microservices focuses on granularity.
