Applied Architecture Patterns on the Microsoft Platform

Pattern description

In this scenario, we need to receive a single inbound request and then, based on the content in that request call, several backend services gather information about the customer and then correlate the responses, aggregate them, and finally send them in a single response message. The web application will then display their personalized information to them. The logical choice is to use an aggregator, which is responsible for the collection of requests, performing transformations (if they are required), and returning the response. All of this also needs to be done in the shortest possible time, as users are not willing to wait more than three to five seconds for this type of information. This pattern is commonly referred to as ...