Not really. Orchestration and choreography are different. Orchestration defines a process, while choreography defines an interaction between two or more parties.
My preferred approach to orchestration is one based on state and rules versus an execution plan. e.g., "Given the current state, what should happen next?" versus "This step just completed (or failed to complete), so this is supposed to happen next." A state/rules-based system has no requirement for a centralized engine to manage the process. Anne On 1/12/07, Stefan Tilkov <[EMAIL PROTECTED]> wrote: > So Anne, would it be fair to say that you think "orchestration" is > fundamentally flawed, and only "choreography" is useful? > > Stefan > -- > Stefan Tilkov, http://www.innoq.com/blog/st/ > > > On Jan 12, 2007, at 4:03 PM, John Evdemon wrote: > > BPEL is an orchestration language – you seem to be describing > > choreography. > > > > > > From: [email protected] > > [mailto:[EMAIL PROTECTED] On Behalf > > Of Anne Thomas Manes > > Sent: Thursday, January 11, 2007 4:57 PM > > To: [email protected] > > Subject: Re: [service-orientated-architecture] Re: Forrester Create > > a Long Acronym > > > > I think BPEL is fundamentally flawed. > > > > > Yahoo! Groups Links > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/service-orientated-architecture/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
