"Introducing SOA Design Patterns", SOA World Magazine (PDF)
"The Case for Single-Purpose Services: Understanding the Non-Agnostic Context and a Strategy for Implementation", SOA Magazine (HTML)
"REST-Inspired SOA Design Patterns", SOA Magazine (HTML)
"Service-Orientation and Object-Orientation Part I: A Comparison of Goals and Concepts", SOA Magazine (HTML)
"Service-Orientation and Object-Orientation Part II: A Comparison of Design Principles", SOA Magazine (HTML)
"Service Facade", InformIT (HTML)
"Non-Agnostic Context", InformIT (HTML)
"Domain Inventory", InformIT (HTML)
"Service Normalization", InformIT (HTML)
"Service Decomposition", InformIT (HTML)
"Canonical Schema", InformIT (HTML)
"Policy Centralization", InformIT (HTML)
How can a service composition facilitate an increased range of service consumer requirements?
Problem
Service compositions are often created to automate a specific parent task. When variations of this task emerge, new compositions are assembled, leading to a potentially bloated collection of service compositions.
Solution
A single service composition can be equipped with multiple endpoints that accommodate a range of service consumers and input values.
Application
Several design techniques can be employed to incorporate new endpoints. The Concurrent Contracts or Contract Denormalization patterns may need to be applied to the composition.
Impacts
To facilitate a range of input values increases the complexity of the composition logic and further increases the governance effort of the composition.
Contributor Notes
This is one of several complex composition governance patterns that I'm working on. It's been successfully applied many times, but I have not yet received a wide enough validation to classify it as a mature and fully provenn pattern.
- Thomas Erl
Arcitura IT Certified Professionals (AITCP)
Arcitura IT Certified Professionals (AITCP)
Arcitura IT Certified Professionals (AITCP) 
Arcitura YouTube Channel
