...
Design the operation and content of the user interfaces to microservice architecture
Avoid designing a single monolithic User Interface that collects data from many of the eHealth microservices into one table or view.
A better option is to separate different user interfaces and workflows in such a way that there is no need to combine large amounts of data in e.g. the same table view.approach could be to:
Target user interface and workflows to only require data from one (or a few) microservices.
Target the workflows so that data is only retrieved when they are to be used.
A suggested approach is the could be to use the same microservices strategy to the user interface itself by e.g. introducing micro-apps or micro frontend patterns.
If the application needs to aggregate information from several FUT Infrastructure services, it should be considered whether the BFF beneficially could cache static or semi-static information.
Use of ”Backend for frontend” or API Gateway patterns
...
See https://ehealth-dk.atlassian.net/wiki/spaces/EDTW/pages/1034354702/Technical+Interactions+with+Services#Caching-on-Searching on caching provided by the infrastructure.
See Client-side caching for recommendations on caching in telemedicine solutions and applications.
...