What are the differences between service orchestration and service choreography from an intra-organization point of view.
Since the thread is old but still writing to it for those who will stumbled here in search of this question as I did. This is much debated question in Service-oriented architecture (SOA) which needs much cleaner explanation for beginners.
Orchestration: Executable Process
Choreography: Multi-party Collaboration
Choreography, in contrast, does not rely on a central coordinator. Rather, each Web service involved in the choreography knows exactly when to execute its operations and with whom to interact. Choreography is a collaborative effort focusing on the exchange of messages in public business processes.
All participants in the choreography need to be aware of the business process, operations to execute, messages to exchange, and the timing of message exchanges.
Choreography vs. Orchestration
From the perspective of composing Web services to execute business processes, orchestration is a more flexible paradigm and has the following advantages over choreography:
The coordination of component processes is centrally managed by a known coordinator.
Web services can be incorporated without their being aware that they are taking part in a larger business process.