From my perspective, there is in fact a distinction between orchestration and composition: Orchestration is one of many different methods to compose services. E.g. you can define compositions at the type level and instantiate it afterwards (that what BPEL does, e.g.); composition at the instance level is possible too (e.g. when an agreement protocol is run between a collection of services); and so on.
----- Ursprüngliche Mail ----
Von: Ashley at Metamaxim <[EMAIL PROTECTED]>
An: [email protected]
Gesendet: Mittwoch, den 19. Juli 2006, 16:10:01 Uhr
Betreff: Re: [service-orientated-architecture] Orchestration, Choreography, and Composition
Von: Ashley at Metamaxim <[EMAIL PROTECTED]>
An: [email protected]
Gesendet: Mittwoch, den 19. Juli 2006, 16:10:01 Uhr
Betreff: Re: [service-orientated-architecture] Orchestration, Choreography, and Composition
Todd wrote:
> I thought I'd turn this into a group exercise and see how all of you
> define it. (i.e., Orchestration, Choreography, and Composition)
> define it. (i.e., Orchestration, Choreography, and Composition)
Excellent. This should be fun!
In my view, Choreography defines a behavioural protocol to which multiple parties must (or should) adhere when engaged in a service based collaboration. I am sure that Steve R-T will give us the definitive definition of Choreography!
Like you, Todd, I am not clear whether there is any real difference between Orchestration and Composition. Perhaps Orchestration is the means by which Composition is achieved?
Rgds
Ashley
SPONSORED LINKS
| Computer software | Computer security software | Computer software program |
| Computer fax software | Computer virus software | Discount computer software |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
