Node architecture at a glance
The building blocks of EOSC Node Slovakia, their public addresses and their current maturity.
The node is composed of a small set of web components under the eosc.sk domain, all reached through one gateway, plus the national research systems operated by CVTI SR.
| Component | Address | Purpose | Status |
|---|---|---|---|
| Landing page | eosc.sk | Entry point, links to resources, services, use cases and tools | Pilot MVP |
| Service catalogue | sc.eosc.sk | Register of node services, public API, PID resolver, harvesting of other nodes | Pilot MVP |
| Monitoring | mon.eosc.sk | Availability and reliability of node components and services, API v1 | Pilot MVP |
| Helpdesk | hd.eosc.sk | Zammad ticketing – single point of contact | Pilot MVP |
| Knowledge base | d1.eosc.sk | Bilingual documentation of the node (this site) | In development |
| FitSM tool | internal | Service management registers and controlled documents | In preparation |
| AAI | Keycloak | Single sign-on for node services (EOSC AAI compatible) | Test environment, production realm in preparation |
| Research resources | KOMIS systems | SK CRIS, SVD, SCIDAP, CREPČ, CREUČ, CRZP | Production / beta |
How the pieces work together
- The catalogue is the source of truth for the services of the node; the landing page reads its production services live from the catalogue API.
- Monitoring probes every public component and every onboarded service and publishes the results in a form the EOSC Federation can harvest.
- The helpdesk receives incidents and requests; the FitSM tool keeps the underlying service management records.
- AAI provides one identity for all node services and connects them to the federated EOSC AAI.