Choreography&orchestration
Download as DOCX, PDF0 likes95 views
Service orchestration involves a centralized business process that coordinates interactions between services by invoking and combining their outputs. Service choreography describes interactions between services through message exchanges without a centralized process. It employs a decentralized approach where each service directly integrates with others. While orchestration has a single point of control, choreography has distributed control with no single manager.
Choreography&orchestration
- 1. What is choreography? How does it differ from orchestration? In choreography there is no business processto control the integration between the systems; each system will directly integrate with one another in the sequence whereas in Orchestration there is a business processwhich controls all theservices (source/Target) which arepart of the integration. Service orchestration Service orchestration represents a singlecentralized executablebusiness process (theorchestrator) that coordinates the interaction among different services.The orchestrator is responsiblefor invokingand combining the services. Service Choreography Service choreography is a global description of the participatingservices,which is defined by the exchange of messages, rules of interaction and agreements between two or more endpoints. Choreography employs a decentralized approach for servicecomposition. Real life example: Service orchestration: you put together several services by a fixed logic.This logic is described ata singleplace. You can imaginea team of people with a manager doing micro-management. The manager precisely tells what, when and who should do. The team members do not care about the entire goal of the job, the manager combines the outputs into a singledeliverable.A practical exampleis a BPEL process.BPEL process contains thelogic,can invoke several services and combinetheir responses into a singleserviceresponse. Service choreography: the decision logic isdistributed,with no centralized point. You can imaginea home, where everybody aims for the common good and works pro-actively without micro-management. Or you can imaginea human body, where different members areinterdependent and work for the common goal.A practical example is event-driven processing,where an agent is activated by an event and does its job.All the agents make a system together. There is no centralized logic.Choreography possibilities may go farther beyond orchestration as it is more aligned with the real world. My opinion is thatwe do not need to distinguish much between these two, as we need to focus on the business logic.Where a singlepointof logic does the job,we do orchestration.Where a problem cannotbe covered by a centralized logic,we have forced to choreography anyway.That is why we often come across orchestration in IT, whereas choreography remains more an academicals conceptand a subjectfor research.And very often we do choreography without actually knowingit,as in the real world.