Master SOA Design Pattern Catalog
|
|
|
|

Domain Inventory (Erl)

|

Home > Foundational Inventory Patterns > Domain Inventory
|
|
How can services be delivered to maximize recomposition when
enterprise-wide standardization is not possible?
|
|
|
|
|

Problem

Establishing an single enterprise service inventory may be
unmanageable for some enterprises, and attempts to do so may
jeopardize the success of an SOA adoption as a whole.
|
|

Solution

Services can be grouped into manageable, domain-specific
service inventories, each of which can be independently
standardized, governed, and owned.
|
|

Application

Inventory domain boundaries need to be carefully established.
|
 |
 |
 |

Impacts

Standardization disparity between domain service inventories
imposes transformation requirements and reduces the overall
benefit potential of the SOA adoption.
|
|
|
|
|

|
| |
|
|
|
An enterprise partitioned into domain service inventories, each representing a
pre-defined domain.
|
|
|
|
|

Related Patterns in This Catalog

Canonical Protocol (Erl),
Canonical Resources (Erl),
Canonical Schema (Erl),
Contract Centralization (Erl),
Cross-Domain Utility Layer (Erl),
Data Model Transformation (Erl),
Enterprise Inventory (Erl),
Inventory Endpoint (Erl),
Logic Centralization (Erl),
Metadata Centralization (Erl),
Service Layers (Erl),
Service Normalization (Erl)
|

|
|
This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy, Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.soabooks.com.
|
|