Difference between revisions of "Information System"
From Gcube Wiki
Luca.frosini (Talk | contribs) (→Definition) |
Luca.frosini (Talk | contribs) (→Non-Functional Requirements) |
||
| Line 35: | Line 35: | ||
* Horizontal Scalability; | * Horizontal Scalability; | ||
* Multi-Tenancy, i.e. a single instance of the technology should be able to serve many “independent” contexts (between the same Application Domain); | * Multi-Tenancy, i.e. a single instance of the technology should be able to serve many “independent” contexts (between the same Application Domain); | ||
| − | * EUPL licence compatibility | + | * EUPL licence compatibility of all its components |
== Architecture == | == Architecture == | ||
Revision as of 15:41, 19 October 2016
The gCube Information System (IS) has been designed to support Research Infrastructure federation.
Contents
Definition
The term ‘research infrastructures’ refers to facilities, resources and related services used by the scientific community to conduct top-level research in their respective fields, ranging from social sciences to astronomy, genomics to nanotechnologies [1]
IS: a registry of the infrastructure offering global and partial view of
- its resources (e.g. computing, storage, services, software, datasets);
- their current status (e.g. up and running, available);
- their relationships with other resources;
- the policies governing their exploitation.
Requirements
Functional Requirements
- Data Definition Language (DDL) for schemas definition (entities and relations).
- Entity and Relation instances must be:
- Univocally identifiable;
- Selective/Partial updatable;
- Validated against the Schema.
- Referential Integrity
- Dynamic Query (no pre-define query)
- Standard Abstraction (desiderata)
- Subscription Notification Support
Non-Functional Requirements
- High Availability (HA);
- Eventual Consistency;
- Horizontal Scalability;
- Multi-Tenancy, i.e. a single instance of the technology should be able to serve many “independent” contexts (between the same Application Domain);
- EUPL licence compatibility of all its components
Architecture
The constituent Components are:
- IS Model
- Information System Resource Registry
- gCube Model
- Information System Resource Manager
- Backend Database (i.e. OrientDB as Graph Database)
