From Modelling to Systematic Deployment of Distributed Active Objects

Abstract

Abstract. In the context of the expansion of actors and active objects, we are still facing a gap between the safety guaranteed by modelling and verification languages and the efficiency of distributed middlewares. In this paper, we reconcile two active object-based languages, ABS and ProActive, that respectively target the aforementioned goals. We compile ABS programs into ProActive, making possible to benefit from the strengths of both languages, while requiring no modification on the source code. After introducing the translational semantics, we establish the properties and the correctness of the translation. Overall, this paper presents an approach to running different active object models in distributed environments, and more generally studies the implementation of programming languages based on active objects.

A Survey of Active Object Languages

“…• An editor with syntax highlighting and integrated build system, including compiler error location • An ABS simulator/interpreter with interactive debugger • Visualization of ABS model execution as a sequence diagram • Code generator backends for Erlang, Haskell, ProActive [54] (see also Section 3.4), Java 8 [83].…”

“…The ProActive backend for ABS 6 generates ProActive code for an ABS source program [54]. The goal of the ProActive backend is to provide a fully working execution of ABS models in distributed environments, with less optimization than necessary for the Java 8 backend.…”

“…Nevertheless, it is possible to write programs that do not perform data-flow synchronization and behave differently. We have formally proven [54] Example and experiments. We use a representative HPC application: pattern matching of a DNA sequence programmed in the MapReduce model [36].…”

Exogenous coordination of concurrent software components with JavaBIP

“…Respectively, when the route is at state on, it can suspend its work by executing the off transition. The on and off transitions are both enforceable (Figure 3: lines 3-4) and are associated with the resumeRoute and suspendRoute methods of the Camel API (Figure 3: lines [19][20][21][22][23][24][25][26][27].…”

“…Several solutions, originating with the Actor model [5,19] and the Active Object pattern [20], have been proposed for dealing with these difficulties, e.g., [21,22,23,24]. (We refer the reader to [25] for an overview.) By restricting the coordination mechanisms to asynchronous message passing, the Actor model guarantees deadlock-freedom and renders the designed software easily amenable for distribution.…”