HOME > ProActive Programming


ProActive Programming

A Java Active Objects APIs for Parallel, Distributed and Multi-Core Computing



ProActive Programming Architecture
Master-Worker:

a Task-Based API for solving Master-Worker type computations (one Master, many workers).

Monte-Carlo:

a Task-based API similar to Master-Worker, specialized for monte-carlo simulations

Legacy Code Wrapping:

Efficient methods to wrap, couple, and gridify legacy code with ProActive, including MPI or other native codes

SPMD:

SPMD technique is perfect for solving tightly-coupled parallel problems requiring intensive communications (CFD, Maxwell,...). This is an alternative to MPI in Java

File Transfer:

Files can be transmitted from or to a remote node at different stage of the application lifecycle

Web Services:

ProActive Programming Active Objects and GCM components can be exposed as web services without any additional development

Data Spaces:

a virtual file system layer that allow files to be accessed among all Active Objects, accross networks and computers

Security:

Communications can be encrypted using a private/public key mechanism to ensure fully secure data transmissions

GCM:

Grid Component Model API is based on and extends the Fractal model to enable component programming in ProActive.

Fault Tolerance:

Application can be configured to be self-healing and restart automatically from latest valid checkpoint.

Asynchrony:

Calls on Active Objects are asynchronous: an answer, a future, is provided without waiting for the end of the result processing.

Mobility:

Active Objects have the ability to migrate between nodes while the application is running.

Remote Accessibility:

Methods defined by active objects can be called from any point of the application.





 
ActiveEon
Universite de Nice-Sophia Antipolis
INRIA

OW2