Data orchestration and response consolidation
The level of complexity in the data composition of the branch design pattern can be considered one of the highest. The high complexity is due to the fact that, when using the branch, we are using both the composition of data and the orchestration of data, either in alternation or simultaneously.
Using the branch as the design pattern, the most common scenario is that the composition of the data occurs in the internal layer of microservices, and, obviously, the data orchestration in the public facing layer. It is worth remembering that a more complex data search implies more time and machine resources to create a response with total integrity.
In the following diagram, we have a process where data composition is being performed in the internal layer, and the orchestration of data in the public facing layer:
Let's understand the flow of the diagram we just observed:
- First, the Microservice Aggregator receives a request from the API and needs to consolidate...
