Introduction to OGSA-DAI Services

Karasavvas, Konstantinos; Antonioletti, Mario; Atkinson, Malcolm; Hong, Neil Chue; Sugden, Tom; Hume, Alastair; Jackson, Mike; Krause, Amrey; Palansuriya, Charaka

doi:10.1007/11423287_1

Cited by 63 publications

(29 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…OGSA-DAI [13] is a middleware product which supports the exposure of data resources on to Grids. This middleware facilitates data streaming between local OGSA-DAI instances.…”

Section: Other Relevant Techniquesmentioning

confidence: 99%

The Circulate architecture: avoiding workflow bottlenecks caused by centralised orchestration

2009

View full text Add to dashboard Cite

As the number of services and the size of data involved in workflows increases, centralised orchestration techniques are reaching the limits of scalability. In the classic orchestration model, all data passes through a centralised engine, which results in unnecessary data transfer, wasted bandwidth and the engine to become a bottleneck to the execution of a workflow.This paper presents and evaluates the Circulate architecture which maintains the robustness and simplicity of centralised orchestration, but facilitates choreography by allowing services to exchange data directly with one another. Circulate could be realised within any existing workflow framework, in this paper, we focus on WS-Circulate, a Web services based implementation.Taking inspiration from the Montage workflow, a number of common workflow patterns (sequence, fan-in and fanout), input to output data size relationships and network configurations are identified and evaluated. The performance analysis concludes that a substantial reduction in communication overhead results in a 2-4 fold performance benefit across all patterns. An end-to-end pattern through the Montage workflow results in an 8 fold performance benefit and demonstrates how the advantage of using the Circulate architecture increases as the complexity of a workflow grows.

show abstract

“…OGSA-DAI [13] is a middleware product which supports the exposure of data resources on to Grids. This middleware facilitates data streaming between local OGSA-DAI instances.…”

Section: Other Relevant Techniquesmentioning

confidence: 99%

The Circulate architecture: avoiding workflow bottlenecks caused by centralised orchestration

2009

View full text Add to dashboard Cite

show abstract

“…The implementation of an environmental data access system that incorporates the ESSE search engine had been based on the OGSA-DAI framework [14,25], the emerging standard for representing databases in Grids.…”

Section: Ogdsa-dai Environmental Data Servicesmentioning

confidence: 99%

Integrating and mining distributed environmental archives on Grids

Zhizhin

Kihn

Redmon

et al. 2007

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYThe solar-terrestrial physics distributed database for the ICSU World Data Centers, and the NCEP/NCAR climate re-analysis data have been integrated into standard Grid environments using the OGSA-DAI framework. A set of algorithms and software tools for distributed querying and mining environmental archives using the UNIDATA Common Data Model concepts has been developed. In addition, the toolkit enables querying the data using meaningful 'human linguistic' terms.

show abstract

“…Triana can distribute sections of a workflow to remote machines through a connected peer-to-peer network. OGSA-DAI [16] middleware supports the exposure of data resources on to Grids and facilitates data streaming between local OGSA-DAI instances. Grid Services Flow Language (GSFL) [19] addresses some of the issues discussed in this paper in the context of Grid services, in particular services adopt a peer-to-peer data flow model.…”

Section: Techniques In Data Flow Optimisationmentioning

confidence: 99%

The benefits of service choreography for data-intensive computing

Barker

Besana

Robertson

et al. 2009

Proceedings of the 7th International Workshop on Challenges of Large Applications in Distributed Environments

View full text Add to dashboard Cite

As the number of services and the size of data involved in workflows increases, centralised orchestration techniques are reaching the limits of scalability. In the classic orchestration model, all data pass through a centralised engine, which results in unnecessary data transfer, wasted bandwidth and the engine to become a bottleneck to the execution of a workflow. Choreography techniques, although more complex to model offer a decentralised alternative and are the optimal architecture for data-centric workflows; data are passed directly to where they are required, at the next service in the workflow.While orchestration is the dominant architectural approach, there are relatively few choreography languages and even fewer concrete implementations. This papers contributions are twofold. Firstly we argue the case for choreography in data-intensive computing, and demonstrate through workflow patterns the advantages in terms of scalability when a choreography architecture is adopted. Secondly we introduce the Light Weight Coordination Calculus (LCC), a type of process calculus used to formally define choreographies, and the OpenKnowledge framework, a choreography-based architecture, providing the functionality for peers to coordinate in an open peer-to-peer system. Through LCC and the OpenKnowledge framework we practically demonstrate how choreography can be achieved in a lightweight manner with a comparatively simple process language.

show abstract

Introduction to OGSA-DAI Services

Cited by 63 publications

References 2 publications

The Circulate architecture: avoiding workflow bottlenecks caused by centralised orchestration

The Circulate architecture: avoiding workflow bottlenecks caused by centralised orchestration

Integrating and mining distributed environmental archives on Grids

The benefits of service choreography for data-intensive computing

Contact Info

Product

Resources

About