Aggregator Provider Pattern is an extension of Provider Pattern, which enables us to create and utilize multiple instances of the class having the same provider interface. In this pattern, there is an Aggregator class which implements the provider interface and contains a collection of instances of classes having the same provider interface.
The underlying caller class of this aggregator is simply unaware of how many provider instances the caller Provider Aggregator contains, but all of the provider instances will be utilized with a single invocation from the caller class.
Comparison with Provider Pattern
Provider Aggregator Pattern is fully compatible with the existing Provider Pattern and the power of provider pattern can be easily extended to use multiple providers concurrently without any modification on the caller classes that were using a provider.
In short, Provider Pattern is concerned with the utilization of one of the available providers; whereas Aggregator Provider Pattern is concerned with the utilization of all of the available providers at the same time.
Aggregator Provider Pattern is useful when we need a configurable framework to add/remove multiple services used by one caller/user. For instance, we can have Logger Provider framework, where we need log information to be saved in text files, save to database and sent to email addresses and so on. Having an easy configurable framework along with Aggregator Provider Pattern will enable us to add or remove more services without requiring the code modification in the code that uses this provider.
Regarding the example case that has just been described can utilize the Aggregator Provider Pattern, by creating the classes as illustrated above. The code snippet below shows a basic usage of this pattern, where the last line will perform the log operation based on a list of log providers loaded in the aggregator class dynamically.
Download the latest white paper and samples from MSDN Code Gallery.