EGI Document 3495-v3

EOSC-hub D10.4 EOSC Hub Technical Architecture and standards roadmap v2

Document #:
Document type:
Submitted by:
Updated by:
Document Created:
28 Aug 2019, 15:19
Contents Revised:
04 Feb 2020, 13:48
Metadata Revised:
04 Feb 2020, 13:48
Viewable by:
  • Public document
Modifiable by:

Quick Links:
Latest Version

Other Versions:
25 Jun 2021, 15:42
09 Mar 2020, 17:10
23 Jan 2020, 13:50
28 Aug 2019, 15:28
28 Aug 2019, 15:19
This document describes the EOSC-hub contribution to the definition of the EOSC Technical Architecture, which is currently being developed by the EOSC architecture Working Group. It is based on the concepts of service interoperability and end-to-end composition of services and foresees the definition of a reference architecture in which EOSC building blocks and the main functions, interfaces, APIs and standards are identified. This architecture is expected to facilitate access to services, lower the barriers to integrate and composes services and promote the usage of services between adjacent communities.
As a basis for the proposed architecture, service categories have been introduced, mapping their functions, relationships and organisation to the kinds of services required for the federating core of EOSC and the external EOSC service portfolio. The concept of the end-to-end composition of services has been presented, highlighting the most common integration scenarios. Leveraging the defined service categories and on the concepts of service interoperability and composition, a reference EOSC Technical Architecture has been defined identifying a hierarchical structure where the first level relies on service categories (Federation & Access enabling,, Common and Thematic), the second level introduces functional categories, that groups technical functions to facilitate their identification, and the third is made of the technical functions that has been called building blocks.
EOSC-hub is working on defining the building blocks of the architecture for each service type and specified a common approach to complete this task. It foresees the identification of the main building blocks/technical functions in each service category and, for each of those, the definition of a technical specification that includes a high-level architecture, suggested EOSC standards and APIs and interoperability guidelines. As a consequence, interoperability between services compliant with the EOSC specifications will be easier to be achieved.

DocDB, Contact: Document Database Administrators