SOA Design Patterns by Thomas Erl
For more information visit: www.soapatterns.com
Related Publications
"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 services be designed to understand proprietary policy assertions?
Problem
The proprietary vocabularies commonly used by service contract policy assertions to express internal business rules and requirements may be foreign to service consumers, thereby compromising interoperability.
Solution
The vocabularies used by service contract policy assertions become standardized across all services within an inventory boundary.
Application
Policy assertion vocabularies are carefully defined and maintained and the application of design standards ensures that each vocabulary is centralized across an inventory.
Impacts
Vocabulary standardization requires extra effort in terms of the long-term governance of the vocabularies and the enforcement of their usage.
Contributor Notes
I see the need for this design pattern in the future, but support for policy vocabularies is not yet sufficiently mature.
- Thomas Erl
