...
This is the scenario that depicts the advantages of the aggregation pattern. If you build an application, or use one of our templates that is built on it, you will notice that you can on demand query It provides for an on-demand query across multiple systems, merge merges the data set, and do as you please with it.For example, you can build an integration app which queries the various systems, merges the data and then produces a report. This way you provides for aggregation
Using this approach we can avoid having a separate database and you can have the report arrive in a format like .csv or the format of your choice. You can place the report in the location where reports are stored directly.
...
The aggregation pattern derives its value from allowing you to extract and process data from multiple systems in one united application. This means The benefit is that the data is up to date at the time that you need it, does not get replicated, and can be processed or merged to produce the dataset you want.
...
The aggregation pattern is valuable if you are creating orchestration APIs to “modernize” legacy systems, especially when you are creating an API which that gets data from multiple systems, and then processes it into one response. Another use case is creating reports or dashboards that pull data from multiple systems and create an experience with that data.
Finally, you may have systems that you use for compliance or auditing purposes which that need to have related data from multiple systems. The aggregation pattern is helpful in ensuring that your compliance data lives in one system but can be the amalgamation of relevant data from multiple systems. You can therefore reduce the amount of learning that needs to take place across the various systems to ensure you have visibility into what is going on.