COMPSs relies on a Storage API to enable the interation with persistent storage frameworks (storage_architecture), which is composed by two main modules: Storage Object Interface (SOI) and Storage Runtime Interface (SRI)
Any COMPSs application aimed at using a persistent storage framework has to include calls to:
- The SOI in order to define the data model (see
Sections/06_Persistent_Storage/01_Storage_integration/01_Data_model:Defining the data model), and relies on COMPSs, which interacts with the persistent storage framework through the SRI.- The SRI in order to interact directly with the storage backend (e.g. retrieve data, etc.) (see
Sections/06_Persistent_Storage/01_Storage_integration/02_Interact_with_storage:Interacting with the persistent storage).
In addition, it must be taken into account that the execution of an application using a persistent storage framework requires some specific flags in runcompss and enqueue_compss (see Sections/06_Persistent_Storage/01_Storage_integration/03_Running_with_storage:Running with persistent storage).
Currently, there exists storage interfaces for dataClay, Hecuba and Redis. They are thoroughly described from the developer and user point of view in Sections:
Sections/06_Persistent_Storage/02_COMPSs_dataClay:COMPSs + dataClaySections/06_Persistent_Storage/03_COMPSs_Hecuba:COMPSs + HecubaSections/06_Persistent_Storage/04_COMPSs_Redis:COMPSs + Redis
The interface is open to any other storage framework by implementing the required functionalities described in Sections/06_Persistent_Storage/05_Own_interface:Implement your own Storage interface for COMPSs.
01_Storage_integration/01_Data_model 01_Storage_integration/02_Interact_with_storage 01_Storage_integration/03_Running_with_storage