Often, a microservice in your business is not able to provide a complete solution to the application, and compiling information with other domains may be necessary. The chained design pattern was developed to respond to and supply this demand by providing a single response to the request made for the application.
This behavior is relatively similar to that of the aggregator design pattern because it aims to provide a single access point for information. However, the way the response to the request is composed has very different characteristics.
First, let's remember how the aggregator design pattern works, so we can clarify the differences between the patterns.
The aggregator has only one access point for the load balancer, which is an orchestrator, which is responsible for aggregating and organizing data in response to a particular request.
After receiving the request, the orchestrator evaluates and triggers concurrent processes for the microservices responsible for...