In a Service Oriented Architecture (SOA) services are interacting by exchanging messages, i.e., by combining services more complex services are created. Orchestration is concerned with the composition of such services seen from the viewpoint of single service.
The terms “orchestration” and “choreography” describe two aspects of integrating services to create business processes [2, 3]. The two terms overlap somewhat and the distinction is subject to discussion. Orchestration and choreography can be seen as different “perspectives.” Choreography is concerned with the exchange of messages between those services and is often be characterized by analogy “Dancers dance following a global scenario without a single point of control.” Orchestration is concerned with the interactions of a single service with its environment. Here an analogy can also be used. In orchestration, there is someone, “the conductor”, who tells everybody in the orchestra what to do and makes sure...
- 1.Alves A, Arkin A, Askary S, Barreto C, Bloch B, Curbera F, Ford M, Goland Y, Guzar A, Kartha N, Liu CK, Khalaf R, Koenig D, Marin M, Mehta V, Thatte S, Rijn D, Yendluri P, Yiu A. Web services business process execution language version 2.0 (OASIS Standard). WS-BPEL TC OASIS; 2007. http://docs.oasis-open.org/wsbpel/2.0/wsbpel-v2.0.html
- 3.Weske M. Business process management: concepts, languages, architectures. Berlin: Springer; 2007.Google Scholar