Tuesday, May 09, 2006
Aggregate Component Pattern
Microsoft Framework team introduces a pattern called "Aggregate Component" which has a similarity to a Facade pattern.
The purpose of this pattern is to enable user of the framework to only deal with one simple component to accomplish a particular task, ie. message queueing etc.
User of the API doesn't have to care about other components that have been encapsulated inside the "aggregate" component.
Some concerns of this approach are:
- It allows users to create object in inconsistent state, which can be remedied by throwing an exception when a user try to call the object with invalid state.
- The component settings need to be done in simple way, providing a lot of default value, otherwise, the benefit is reduced.
- It works well for entry level user, since, some of the default settings might not promote the most efficient way of using the framework.
The purpose of this pattern is to enable user of the framework to only deal with one simple component to accomplish a particular task, ie. message queueing etc.
User of the API doesn't have to care about other components that have been encapsulated inside the "aggregate" component.
Some concerns of this approach are:
- It allows users to create object in inconsistent state, which can be remedied by throwing an exception when a user try to call the object with invalid state.
- The component settings need to be done in simple way, providing a lot of default value, otherwise, the benefit is reduced.
- It works well for entry level user, since, some of the default settings might not promote the most efficient way of using the framework.
# posted by The Fighting Illini @ 10:43 AM 
