Difference between revisions of "Data Management APIs"
From Gcube Wiki
(→Key Features) |
(→Key Features) |
||
Line 7: | Line 7: | ||
==Key Features== | ==Key Features== | ||
;Consistency securing across different client APIs | ;Consistency securing across different client APIs | ||
− | :Uniformity in inputs and outpus, context management, fault management, operation modes provision | + | :Uniformity for APIs across standalone framework layers in inputs and outpus, context management, fault management, operation modes provision, etc. |
;Transparent system resource management | ;Transparent system resource management |
Revision as of 12:01, 29 June 2012
Overview
gCube Data Management APIs provide access to the management of the e-Infrastructure resources by facilitating the integration of technology external to the e-Infrastructure. Towards the directions of openness and interoperability, management APIs move along:
- the adoption of standards
- the implementation of a variety of protocols (e.g. Java, REST, SOAP, depending on the need and relevance)
- the compliance to the Integration and Interoperability Facilities Framework
Key Features
- Consistency securing across different client APIs
- Uniformity for APIs across standalone framework layers in inputs and outpus, context management, fault management, operation modes provision, etc.
- Transparent system resource management
- Design of APIs simplifying client usage, with respect to requirements specific to the system
- Environment propagation
- Operational information among services transparently propagated over a range of protocols (SOAP, HTTP/S, and more)
- Testability endorsement
- Design solutions that facilitate testing for clients
- Support to standards
- Crucial functionalities are accessible via recognized standards in order to enhance interoperability
- Stability ensuring
Subsystems
Data Management APIs are collectively delivered by the following sets of software subsystems: