Difference between revisions of "Data Management APIs"

From Gcube Wiki
Jump to: navigation, search
(Key Features)
(Key Features)
Line 9: Line 9:
 
:Uniformity for APIs across standalone framework layers in inputs and outpus, context management, fault management, operation modes provision, etc.
 
: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 integration
 
:Design of APIs simplifying client usage, with respect to requirements specific to the system
 
:Design of APIs simplifying client usage, with respect to requirements specific to the system
  
Line 15: Line 15:
 
:Operational information among services transparently propagated over a range of protocols (SOAP, HTTP/S, and more)
 
:Operational information among services transparently propagated over a range of protocols (SOAP, HTTP/S, and more)
  
;Testability endorsement
+
;Testability ensuring
 
:Design solutions that facilitate testing for clients
 
:Design solutions that facilitate testing for clients
  
Line 21: Line 21:
 
:Crucial functionalities are accessible via recognized standards in order to enhance interoperability
 
:Crucial functionalities are accessible via recognized standards in order to enhance interoperability
  
;Stability ensuring
+
;Compatibility endorsement
:
+
:Exploitation of framework simplifying building of modular systems
 +
 
 +
;
  
 
==Subsystems==
 
==Subsystems==

Revision as of 13:27, 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:

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 integration
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 ensuring
Design solutions that facilitate testing for clients
Support to standards
Crucial functionalities are accessible via recognized standards in order to enhance interoperability
Compatibility endorsement
Exploitation of framework simplifying building of modular systems

Subsystems

Data Management APIs are collectively delivered by the following sets of software subsystems:

Tree/Document Management APIs

Data Access and Storage APIs

Data Transfer APIs