In order to make COMPSs capable of orchestrating applications that process big amounts of data, the data management is being extended both at programming model and runtime system levels. In this sense, we are aimed at working on integrating COMPSs with persistent object storage platforms, making the most of distributed, fault-tolerant and efficient storage possiblities.

The main mission of the aforementioned platforms is to facilitate the access to data as much as possible. So that any function in a COMPSs application should be able to seamlessly work with objects in memory or with persistent objects, with no need to be adapted for each case.

The following picture depicts the overall structure of the current architecture. COMPSs applications are located at the top of the stack, and the tasks they generate are processed by the COMPSs runtime system. COMPSs runtime relies on a Storage API in order to create, delete, insert, retrieve and iterate over persistent data.

The Storage API can be implemented by multiple Storage Backends. The Storage Backend is responsible for storing data in a set of distributed resources, managing data format and organisation and optimising data queries. Currently, the Storage API does not provide any functions to manage transactions, so the consistency guarantees offered to applications are inherited from the Storage Backend used.

Our motivations are to make possible to handle big objects (too big to fit in the memory of a single node), offer a simple mechanism to access those objects and manage their persistency, and keep all data management transparent to the developer.