2009 First International Conference on Intensive Applications and Services 2009
DOI: 10.1109/intensive.2009.8
|View full text |Cite
|
Sign up to set email alerts
|

Scalable Services Orchestration with Continuation-Passing Messaging

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
10
0

Year Published

2009
2009
2020
2020

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(10 citation statements)
references
References 9 publications
0
10
0
Order By: Relevance
“…In a different proposal in [23], component services are upgraded to workflow engines. They can identify and perform their tasks (including data transfer) by examining the workflow description (i.e., script), like in choreography.…”
Section: Related Workmentioning
confidence: 99%
“…In a different proposal in [23], component services are upgraded to workflow engines. They can identify and perform their tasks (including data transfer) by examining the workflow description (i.e., script), like in choreography.…”
Section: Related Workmentioning
confidence: 99%
“…Advanced dependency management is not required because each service only has a single dependency, namely the previous service, and process fragmentation is straight forward. Approaches to distributed coordination among service providers are based on direct interaction [10], [11] or use shared tuplespaces [12], [13]. The advantage of shared tuplespaces is that communicating parties do not have to be present at the same time, as they anonymously exchange data and control via a piece of shared memory.…”
Section: Related Workmentioning
confidence: 99%
“…However, shared tuplespaces consume high resources and suffer from efficiency and scalability issues due to global synchronisation requirements [14]. Continuation passing [10] and migration of process descriptions [11] use direct interaction and are similar to our approach of transferring control among service providers. Continuation passing allocates control hop-by-hop and activates subsequent service providers by passing the remainder of the execution along with asynchronous messages.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In contrast to the above mentioned centralized approaches, Yu et al [8] adopted a decentralized choreogra- phy messaging style for executing a BPEL workflow. In this setup, the message that is passed to a component service instructs it to carry out the immediate activity of the workflow, and to subsequently continue the remaining activities of the workflow by invoking the next service.…”
Section: Introduction and Related Workmentioning
confidence: 99%