Executable choreography: Difference between revisions

Revision as of 07:24, 14 June 2018

Revision as of 22:47, 14 June 2018

Line 1:

{{AFC submission|td||ts=20180614072144nn|u=Damiancatalin|ns=118|demodecliner=The Mighty Glen|declinets=20180614224734|ts=20180614072420}} <!-- Important, doDo not remove this line before article has been created.! -->

[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.]

Line 9:

* '''Serverless choreographies''' - serverless execution is a cloud computing model in which the cloud provider (or cloud nodes in the blockchain situation) dynamically manages the allocation of computing resources.

* '''Choreographic smart contract''' - a subtype of serverless choreographies, a choreography that use  as input and outputs only data from PrivateSky’s blockchains.

== References ==

<!-- Inline citations added to your article will automatically display here. See https://en.wikipedia.org/wiki/WP:REFB for instructions on how to add citations. -->

{{reflist}}

{{AFC submission|||ts=20180614072420|u=Damiancatalin|ns=118}}