2010 IEEE International Conference on Web Services 2010
DOI: 10.1109/icws.2010.71
|View full text |Cite
|
Sign up to set email alerts
|

Optimizing the Data-Traffic of Centrally Coordinated Scientific Workflow Systems

Abstract: Scientific workflow systems facilitate scientific experiments by integrating and coordinating geographically distributed data and algorithmic services in a loosely coupled manner. Most scientific workflow-engines use centralized coordination as the choice of approach for executing workflows, requiring the coordinator (i.e., workflow-engine) to send and receive all input and output data of component services. Such indirect data communication between the component services increases the data-traffic of the coord… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

0
9
0

Year Published

2012
2012
2019
2019

Publication Types

Select...
3
2

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(9 citation statements)
references
References 9 publications
0
9
0
Order By: Relevance
“…An empirical evaluation of the proposed PDFD vs published DFD given in Subramanian et al (2010Subramanian et al ( , 2012. The DFD approach is briefly described in Section 2.…”
Section: Pipelined Data-flowmentioning
confidence: 99%
See 1 more Smart Citation
“…An empirical evaluation of the proposed PDFD vs published DFD given in Subramanian et al (2010Subramanian et al ( , 2012. The DFD approach is briefly described in Section 2.…”
Section: Pipelined Data-flowmentioning
confidence: 99%
“…In regular orchestration, data from one service is passed to the next service through the workflow coordinator. To optimize orchestrated workflow performance, in a previous paper (Subramanian et al, 2010) we proposed DFD, which allows data to flow directly from one service to the next. Furthermore, we applied DFD to SOAP Web services in a follow up paper (Subramanian et al, 2012).…”
Section: Introductionmentioning
confidence: 99%
“…In a Classical orchestration approach, the workflow is executed by moving all the data between services of the workflow via the orchestrator. This indirect movement of data between the services of the workflow decreases the workflow performance (Subramanian et al 2010). The performance decreases further when the orchestrated workflow has to handle big-data in it.…”
Section: Introductionmentioning
confidence: 99%
“…The data-flow delegation happens on the fly according to the workflow requirements, i.e., the coordinator instructs the component services where the input data will be sent from, and where to send the output data. In this paper, we show that the data-flow delegation proposed in our previous paper [20] can be applied to delegate data between plain SOAP web services. We used concept of operation overloading to inject data-flow delegation instructions into service requests.…”
Section: Introductionmentioning
confidence: 99%
“…Mediating the large data-transfer between the component services increases use of the coordinator's resources excessively (e.g., memory, bandwidth), and increases the workflow execution time. In [20], we have proposed an approach called DataFlow Delegation to overcome this data-flow bottleneck. In that paper, we have given a theoretical foundation, for separating the control and the data-flow in a workflow execution in order to delegate the data-flow responsibilities to the component services.…”
Section: Introductionmentioning
confidence: 99%