Posts

post

Projects

project

Videos

video

Podcasts

podcast

People

person

Events

event

Publications

publication

Solutions

solution

Services

service

Pages

page

Partners

partner

Case Studies

case-study

Default Confirmation

General Contact form

Newsletter form

Project Management Office Contact Form

Newsletter subscription

EGI DIH and Business Contact Form

Share your news

Services, Solutions and Support Team Contact Form

Communications Team Contact Form

Director Finances and HR Contact Form

Training Team Contact Form

EGI DIH Application form

Form Test

Service order form

test

EOSC DIH Tender

core/freeform

Blog article written by Diego Scardaci, Senior User Community Support and Outreach Officer at the EGI Foundation.
EOSC-hub has produced a <a href="https://www.eosc-hub.eu/deliverable/d104-eosc-hub-technical-architecture-and-standards-roadmap" target="_blank" rel="noopener noreferrer">deliverable</a> which proposes an open and participatory approach to the definition of the EOSC Technical Architecture.
<a href="http://eosc-hub.eu/eosc-technical-architecture-survey" target="_blank" rel="noopener noreferrer">Your feedback is very welcome &#8211; participate in the survey now!</a>
The document proposes the definition of a reference Technical Architecture for EOSC that facilitates access to services, lower barriers to integrate and composes services and promotes the usage of services between adjacent communities. This is achieved identifying key technical functions, named building blocks, for each of the EOSC service category (Federation, Access Enabling, Common and Thematic) and defining related technical specifications that include an high-level architecture, endorsed EOSC standards and APIs and interoperability guidelines. In this way, EOSC ‘compliant’ services will offer well-established and documented interfaces for usage and integration, based on well-known standard or APIs, facilitating:
<ul>
<li>their exploitation from user communities willing to create new scientific services that could rely on well-established and documented interfaces for the integration. An example of exploitation of EOSC services is when a community creates a new scientific workflow reusing EOSC federation and common services, like AAI, accounting, Cloud orchestrator and/or data management solutions.</li>
<li>the combined usage of EOSC services. Indeed the adoption of well-known standards and interfaces will very-likely reduce the cost to integrate services. For example, two accounting infrastructures can be made easily interoperable if they use the same standard usage record format, in such case accounting data extracted from them can be merged and presented in a unique view. Another example is about data processing and data management services implementing compliant interfaces that enable a jointly usage by a thematic services.</li>
</ul>
The proposal in the <a href="https://documents.egi.eu/public/ShowDocument?docid=3495" target="_blank" rel="noopener">deliverable</a> is put forward for further discussion, and feedback is welcome. We propose this document to initiate a community activity to populate the EOSC technical architecture identifying key technical functions/building blocks per service category and, for each of those, defining a technical specification that includes an high-level architecture, suggested EOSC standards, APIs and interoperability guidelines. A consultation on the proposals has been launched to collect feedback from stakeholders. <a href="https://eosc-hub.eu/eosc-technical-architecture-survey" target="_blank" rel="noopener noreferrer">Fill in the survey and send us your feedback</a>! The survey is open until the end of September.

Technical Solutions Lead

Diego Scardaci

Have your say on an EOSC-hub proposal for the EOSC technical architecture

<a href="https://www.egi.eu/terms-of-use/">terms of use</a>  |  <a href="https://www.egi.eu/privacy-notice/">data protection</a> | <a href="https://www.egi.eu/egi-foundation/certifications">certifications </a>