Context: My application is comprised of multiple services, each offering a set of UI screens with Angular. The application has a single URL, a navigation menu, and when selecting a menu, a new tab is created in this main page and the content of the page is displayed within this tab. We can still see the main header on top of the screen with the navigation menu, the logout button and a couple of other things. Problem: Today the way I achieve this is by compiling all of the screens in a single step, and packaging them in a single web server (which I call "gateway"). This is causing me some issues. For example, I have a service, let's call it "Referential Service" or RS, which provides screens to maintain some referential data. This Referential Service is a common service used by 2 different main applications. These 2 applications have different URLs as they are meant for different users. I don't want users to have to go to a third URL to see the RS screens. I need to show the RS screens within the main UI of the 2 applications. See below an example of the main application's UI: UI screenshot The only way I know to do that is to compile and package all the screens (the main app screens + the RS screens) into a single webapp (gateway service) for each solution => the RS screens are essentially duplicated in 2 web servers. I still have the separate underlying backend RS service to provide data for the screens via REST APIs, but its Angular screens are packaged inside the main application's gateway. This can cause some backwards compatibility issues if the 2 main applications are on different releases, i.e. they embed different versions of the RS screens, but there is a single RS backend serving both versions of the UI: Current packaging and deployment Requirement: I am looking for a way to be more modular: I want the RS screens to be packaged inside the RS service itself. But I still want the Solution 1/2 webapps to show the RS screens under the same URL, under the same Angular shell, like on the first screenshot. Desired packaging and deployment I do not want the Ref Service screens to be shown in a different URL, or to pop-up in a different tab of the web browser. Is there a way to achieve this, i.e. when a user is on the main application's URL, they go to the navigation menu, select a menu of an RS screen, this screen's static UI files are retrieved from the RS service, but they are displayed inside the main screen of the main app => for the user it looks like everything is in the same application, even though different modules/services are packaging and providing the UI. Thank you Continue reading...
