|
Introduction to SOA Types & Design Patterns
|
|
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.
|
|
|
Chapter 5: Basic Service Inventory Design Pattern Language
|
Home >
Chapter 5 Overview >
5.2 Inventory Boundary Design Patterns
|
Inventory Boundary Design Patterns
As explained in Chapter 3, an inventory of services represents an independently standardized and governed collection of related services and each such inventory is supported by its own, individual service-oriented technology architecture
implementation.
Therefore, a fundamental step in the creation of any service inventory is the definition of its scope in relation to the enterprise within which it resides.
The Enterprise Inventory and Domain Inventory design patterns follow the inventory context patterns to establish the boundary of the service inventory. There is no suggested sequence for these patterns, as only one of these two patterns can be applied within a given environment.
Enterprise Inventory
How can services be delivered to maximize recomposition?
|
|
Domain Inventory
How can services be delivered to maximize recomposition when enterprise-wide standardization is not possible?
|
|
|
|
Prev | Next
|
|
|
