In microservices, we have a tendency to break our business features into tiny items as separate services, and these services are hosted on completely different servers. Each service has its own information (sometimes services share one database), and the incoming data to these services contains this information. Sometimes, it's necessary to mix the details of the data that is coming from the services. This data requires the patron and this job/task to be done at the service level only. Data collaboration is the responsibility of the system and not of the patron.
To handle such cases, we can use the Aggregator pattern. As its name suggests, it aggregates or combines the information and returns the final response. With the assistance of the Aggregator pattern, we will mix the responses of two or more services, apply any business logic (if required...