I need to implement a business process that performs 4 steps e.g.
- An event calls Service A
- Use the response of Service A to Call Service B
- Use the response of Service B to Call Service C
- Use the response of Service c to Call Service D
I have implemented the above using a central Orchestration microservice in the past. Where the Orchestration Springboot microservice holds the logic and manages the E2E business process (steps 1-4).
My questions:
- When is the use of an orchestrator service good practice i.e. a central microservice communicating to external services and passing the output of one service as input to the next dependent service?
- If one or more of steps 1-4 is a messaging interaction based on pub/sub or standard queue, what will be the best approach to implement the business process 1-4?
- If steps 1-4 is all synchronous service call, could I still use choreography with service communication based on events pub/sub and queues?
- When is a workflow tool like Airflow suitable for this kind of multi-microservice interaction to realize a business process?
Aucun commentaire:
Enregistrer un commentaire