ChorSystem: A Message-Based System for the Life Cycle Management of Choreographies

Abstract

Service choreographies are commonly used as the means for enabling inter-organizational collaboration by providing a global view on the message exchange between involved participants. Choreographies are ideal for a number of application domains that are classified under the Collaborative, Dynamic & Complex (CDC) systems area. System users in these application domains require facilities to control the execution of a choreography instance such as suspending, resuming or terminating, and thus actively control its life cycle. We support this requirement by introducing the ChorSystem, a system capable of managing the complete life cycle of choreographies from choreography modeling, through deployment, to execution and monitoring. The performance evaluation of the life cycle operations shows that the ChorSystem introduces an acceptable performance overhead compared to purely script-based scenarios, while gaining the abilities to control the choreography life cycle.

A Service Discovery Solution for Edge Choreography-Based Distributed Embedded Systems

“…The choreography model applies TraDE modeling extensions to replace the traditional message-based data exchange by a data-aware choreography [ 30 ]. Previous works of TraDe authors include the ChorSystem platform [ 23 ].…”

Model-as-You-Go for Choreographies: Rewinding and Repeating Scientific Choreographies

“…If the model of a i (model(a i )) is a loop activity, the sub-routine λ (handleLoopActivity, cf. Definition 15 and Algorithm 4) is invoked instead (lines [15][16][17]. Definition 13 (Function χ).…”

“…If there exists already a rewinding point for p i r (line 10), it is checked if (i) the old rewinding point would be a successor of the new one (using the succ function defined in Definition 14 below) or if (ii) both are in parallel branches. In case (i) the old rewinding point activity instance is removed before the new rewinding point is added and in case (ii) both are kept (lines [11][12][13][14][15][16][17][18][19]. In both cases, ρ is invoked recursively afterwards (lines 20-23).…”

“…model(a i ) ∈ A * (cf. Definition 1) (lines [15][16][17]. After the traversal of g i , iter curr is incremented by 1.…”

“…In the following, we show how our approach for rewinding and repeating of choreography logic is realized in our ChorSystem. The service-oriented and message-based ChorSystem enables users to manage the complete life cycle of choreographies from modeling to execution [17]. The life cycle starts with choreography modeling, transformation to and refinement of workflow models.…”