Revision as of 22:47, 14 June 2018 edit The Mighty Glen (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 21,562 edits Declining submission: nn - Submission is about a topic not yet shown to meet general notability guidelines (be more specific if possible) (AFCH 0.9) ← Previous edit		Revision as of 08:42, 16 July 2018 edit undo Damiancatalin (talk \| contribs) 21 edits m edit test Tag: Visual edit Next edit →
Line 3: [https://www.semanticscholar.org/paper/Process-Design-Requirements-Peltz/bba3aae9c34857c4eeedf05c5c69b79bf5364e6f Orchestration always represents control from one party’s perspective. This differs from choreography, which is more collaborative and allows each involved party to describe its part in the interaction.] ByByy service choreography or executable choreographies we understand the composition of two or more services in a decentralized way (uncontrolled by a single entity). Another perspective is to see the [[Orchestration (computing)\|orchestration]] as a local perspective and choreography as a global perspective.'''Executable Choreographies Types:''' * '''Verifiable choreographies''' - for the [[PrivateSky]] project all the executable choreographies are verifiable. The explicit presence of the execution ___location leads to the possibility of developing verification algorithms.

Executable choreography: Difference between revisions