Service Aggregation Overview

compared with
Current by Julien Lesbegueries
on May 07, 2011 09:15.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (5)

View Page History

Service aggregation concerns issues related to the use of several services to perform an application. In the context of SOA, services are considered as unitary bricks that have to be assembled in order to build workflows, corresponding to higher level services for particular business needs. The flexibility is obtained thanks to low coupling inherent in Web Services and standards that structure these workflows.

To summary, this thematic is divided in 2 parts:

* [aggregation:Orchestration], [Orchestration|aggregation:Orchestration Overview], performed by a particular entity, running a workflow (i.e an execution graph) composed of messages reception, control structures and services invokation.

* [aggregation:Choreography], [Choreography|aggregation:Choreography Overview], performed from several entities involved in the workflow, checking interactions and relationships between neighbor partners.


* [EasyBPEL|easybpel:EasyBPEL Overview], to manage WS-BPEL 2.0 standard upon EasyVIPER,
* [EasyBPMN|easybpmn:EasyBPMN Overview], to manage BPMN 2.0 standard upon EasyVIPER,
* [GEasyBPMN|geasybpmndesigner:GEasyBPMNEditor Overview], a web-based GUI to design BPMN workflows.
* [GEasyBPMNEditor|geasybpmneditor:GEasyBPMN Editor - Open source BPMN 2.0 modeler], a web-based GUI to design BPMN workflows.