First steps

COMPSs relies on a Storage API to enable the interation with persistent storage frameworks (Figure 41), which is composed by two main modules: Storage Object Interface (SOI) and Storage Runtime Interface (SRI)

Figure 41 COMPSs with persistent storage architecture

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 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 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 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:

• COMPSs + dataClay
• COMPSs + Hecuba
• COMPSs + Redis

The interface is open to any other storage framework by implementing the required functionalities described in Implement your own Storage interface for COMPSs.