| Sign In/My Account | View Cart |
|
|
Orchestration, Choreography and Choreostration
![]() Jim Alateras The two terms have concise and distinct meaning in the English language but they are used very loosely in computer science (particularly in respect to web services and BPMS). In fact there is so much overlap in our definition of orchestration and choreography that it only serves to confuse the market. There are four specifications, namely BPEL, BPML,. WS-CDL and WSCI, which potentially fall into the orchestration and choreography bucket. From this group of specification I have noted the following, not so interesting point. The Web Services Choreography Description Language specification makes no mention of orchestration but makes extensive use of choreography. The Business Process Execution Language specification mentions neither orchestration or choreography. Finally, the Business Process Modeling Language specification makes a single reference to choreography (via a link to the WSCI specification). There is so much overlap between the specification that we could merge them all into a single specification, dispense with one of the terms or come up with a complete new term like choreostration, without disrupting the market. In the vendor space no one is currently supporting WS-CDL or WSCI and there are only a handful supporting either BPEL or BPML (actually only one that I know off supports BPML). In the customer space who is going to purchase an orchestration engine without so called choreography capabilities or visa versa. Maybe those that will buy a workflow system without BPMS capabilities. Jim Alateras is an independent consultant specializing in open source and emerging technologies. Showing messages 1 through 2 of 2.
Return to weblogs.oreilly.com. Weblog authors are solely responsible for the content and accuracy of their weblogs, including opinions they express, and O'Reilly Media, Inc., disclaims any and all liabililty for that content, its accuracy, and opinions it may contain.
|
|
Sponsored By: |
|||||||||||||
In my mind, orchestration and choreography are connected but don't necessarily overlap. If choreography describes the externally visible behavior of interacting systems (e.g. interfaces), orchestration is the means by which the systems are driven to achieve intended results. The key distinction being that orchestration implies a goal and possibly many decisions to realize that goal whereas choreography represents an array of choices and the consequences of making those choices.
Following this definition, BPEL achieves both by being able to describe both process abstracts and executable processes. BPML also does both while WS-CDL and WSCI focus on choreography; no surprise there.
I agree that customers want both orchestration and choregraphy. What is bread without butter?
cheers,
alex