A pattern captures a commonly recurring solution to a problem (example: Request-Reply pattern[14]). The specification of a pattern describes the problem being addressed, why the problem is important, and any constraints on the solution. Patterns typically emerge from common usage and the application of a particular product or technology.
A pattern can be used to generate customized solutions to a recurring problem in an efficient way. We can do this pattern recognition or development through a process called service oriented modeling.
WebSphere Message Broker version 7 introduced patterns that:
Increase development efficiency because resources are generated from a set of predefined templates
Improve quality through asset reuse and common implementation of functions such as error handling and logging
- The patterns cover a range of categories including file processing, application integration, and message based integration.
Pattern examples
- Request-Reply (RR)
- Aggregation (Ag)
- Sequential (Seq)
No comments:
Post a Comment