WP2: Define integration and architecture guidelines

Lead beneficiary: SCB


This WP will study the architecture possibilities for integrating services, and the features that are important for improving service integration. Dealing with legacy architecture will also be explored through a realistic use case.

Description of the work

This work package will study, explore and describe the different architecture possibilities for integrating services (e.g. orchestration, publish/subscribe, point-to-point, adapters, containers). NSI have different as-is situations and different goals that the to-be architecture should align with. A list of real life examples in NSIs where the situation and goals
differs will be selected and guidance will be provided to show the effect of choosing different integration patterns.
Examples of goals that the architecture should align with could be stronger data and metadata governance or agile production processes. One of the NSI examples should be how to move from a legacy architecture to a service oriented architecture, giving organisation with a lesser service oriented maturity a step-by-step cookbook to modernise their
systems. These examples should be the foundation of the architectural discussion.
Achieving efficient service integration requires more than data and metadata exchange. Other features that are expected in real situations are for instance capabilities for:
- Logging
- Containerization
- Authorisation
- Status monitoring
- Service scaling
The guidance will describe how features like this can be realized using smart architectural patterns rather than being hard coded in to each service.
Guidance on how to integrate services and realise features will also be based on the deliverables from WP1.
Examples will be tested in the sandbox delivered by WP 3.
The deliverables will build on pre-existing documents and guidelines (e.g. from the previous ESSnet on CROS portal or UNECE HLG MOS standards) and propose improvements where appropriate.