...
Shell frontend
The shell frontend is a single page app. It handles security and routing to the individual micro-frontends. The user accesses the shell and from there they can navigate through a menu to the individual micro-frontends. The user never leaves the shell application, but different micro-frontends can be shown. The connection between the shell application and the micro-frontends is very loosely coupled, and only through the users browser. For further information on micro frontends see https://micro-frontends.org/ . The shell application is hosted as a container with a Nginx server, to enable the browser to load the shell frontend. The shell frontend only really runs in the users browser. The way these micro-frontends are loaded into the shell application , is facilitated by the tool Webpack, see also Micro frontends - eHealth Infrastructure Wiki - Confluence (atlassian.net) and Concepts | webpack
The micro-frontends are not loaded before they are needed, in order to maximize performance of the user expirience
Micro frontend
The micro-frontends expose a frontend, tailored to show resources from a single infrastructure service. Currently there are three micro-frontends: careteam, questionnaire and plan. These micro-frontends are exposed by the shell-frontend, and use infrastructure services to deliver resources to the end user. For more information on how to interface from micro-frontend to shell application, read this page : Micro frontends - eHealth Infrastructure Wiki - Confluence (atlassian.net).
The individual micro frontends are hosted as a containers with each their Nginx server, to enable the browser to load the specific micro-frontend. The individual micro-frontend only runs in the users browser.
Common pickers
Among the micro-frontends, there are a need for a shared set of pickers, to make it possible to select and organization, create a timing expression, set measurement thresholds etc. For this a module has been created. The micro-frontends include this module and invoke it using messages in the browser, and will also receive the picked value/setting through a message. For more information on how to utilize pickers from the KAM project , have a look here: Kam-pickers - eHealth Infrastructure Wiki - Confluence (atlassian.net). The set of pickers are hosted as a container with each its own Nginx server, to enable the browser to load the pickers. The pickers only really run in the users browser.
Infrastructure services
The remaining services are all infrastructure services
...