The public review of the manuscript for "SOA Design Patterns" has concluded !
Thank you to all that participated. 234 reviews were received and over 30 new patterns have been contributed, increasing the size of this book by over 50%. The second draft of the manuscript is currently in development.
SOA Design Patterns by Thomas Erl
For more information visit: www.soapatterns.com
Related Publications
Read the article "Introducing SOA Design Patterns" from the June 2008 SOA World Magazine (High-Res PDF).
PLEASE NOTE
The content on this page is from the first draft of the manuscript for the upcoming book "SOA Design Patterns" by Thomas Erl. This version of the manuscript was authored in September, 2007. Since then, the manuscript has undergone significant content and structural changes as a result of an industry-wide review in which hundreds of SOA practitioners participated in addition to SOA vendors and experts from the design patterns community.
You are welcome to use the information on this page for research purposes, but you should assume that most of it will change in the final release of the "SOA Design Patterns" book.
Note also, that as a result of an industry-wide call for participation from December 2007 to February 2008, over 30 new design patterns have been contributed to this book. As they become finalized and are incorporated by the author, concise descriptions will be published on this site, and full descriptions with examples will be made available in the final, printed book.
Due to the volume of new content and changes, the release of the "SOA Design Patterns" book has been postponed to October, 2008. To learn more about the book, visit www.soapatterns.com. To be notified of updates to this site, use the notification form.
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.
Principles
Standardized Service
Contract
Architecture
Inventory, Service
Status
Suspended
Contributor
Thomas Erl
Contributor Notes
I see the need for this
design pattern in the future, but support for policy vocabularies is not yet
sufficiently mature.
