- Service orchestration represents a single centralized executable business process (the orchestrator) that coordinates the interaction among different services.
- The orchestrator is responsible for invoking and combining the services.
- The relationship between all the participating services are described by a single endpoint (i.e., the composite service). The orchestration includes the management of transactions between individual services. Orchestration employs a centralized approach for service composition.
- Firstly, in orchestration, as you know, a central process is responsible for when and how services are invoked. In the case of a synchronous system where the orchestrator makes HTTP calls to services in series, the communication might look something like the following diagram.
- Alternatively, you might wish to take an asynchronous approach, in which a message broker is used to store the information about jobs that the services must complete. In this case, your communication would look something like the following diagram.
- Easy to maintain and manage as we unify the business process at the center.
- In synchronous processing, the flow of the application coordinates efficiently.
- Creating dependency due to coupled services. For example, if service A is down, service B will never be called.
- The orchestrator has the sole responsibility. If it goes down, the processing stops and the application fails.
- We lose visibility since we are not tracking business process.
- Service choreography is a global description of the participating services, which is defined by exchange of messages, rules of interaction and agreements between two or more endpoints. Choreography employs a decentralized approach for service composition.
- The choreography describes the interactions between multiple services, where as orchestration represents control from one party’s perspective. This means that a choreography differs from an orchestration with respect to where the logic that controls the interactions between the services involved should reside.
- This decentralization means that each service is aware of a small piece of the big picture, but only those parts in which the service plays an active role. The services are otherwise unaware of their overall position and relevance concerning the business workflow under execution.
- As you can see, each service is responsible for invoking and responding to any adjacent services as needed. This behavior is also true for asynchronous communication, with the main difference being the inclusion of a message broker instead of direct HTTP calls.
- In this asynchronous approach to workflow choreography, each service subscribes to and publishes specific message types directly, rather than an orchestrator being responsible for mediating communication between services.
- Faster processing as no dependency on central controller.
- Easy to add and update. The services can be removed or added anytime from the event stream.
- As the control is distributed, there is no single point failure.
- Works well with agile delivery model, as teams work on certain services rather than on entire application.
- Several patterns can be used. For example, Event sourcing, where events are stored, and it enables event replay. Command query responsibility segregation (CQRS) can separate read and write activities.
- Complexity is the concerning issue. Each service is independent to identify the logic and react based on the specific data in the event stream.
- Business process is spread out, making it difficult to maintain, manage the overall process.
- Mindset change is prerequisite in the asynchronous approach.
Think :**An Example: E-Commerce Checkout :**
Imagine we have an e-commerce site. When a customer completes the checkout process, a few things need to happen:
- We need to send an email to the customer with their order confirmation.
- We need to send the order to our warehouse so we can begin the shipment.
- If the customer signed up for our rewards program, we need to create a new points balance for them.
It’s important to note that once an order is placed, these next three tasks don’t necessarily need to happen in any particular order. They just need to happen.
- https://stackoverflow.com/questions/4127241/orchestration-vs-choreography#:~:text=The choreography describes the interactions,the services involved should reside.