SOA Patterns > Foundational Inventory Patterns > Domain Inventory
Domain Inventory (Erl)
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.
Architecture
Enterprise, Inventory
An enterprise partitioned into domain service inventories, each representing a pre-defined domain.
Related Patterns in This Catalog
Canonical Protocol, Canonical Resources, Canonical Schema, Contract Centralization, Cross-Domain Utility Layer, Data Model Transformation, Enterprise Inventory, Inventory Endpoint, Logic Centralization, Metadata Centralization, Service Layers, Service Normalization
Related Service-Oriented Computing Goals
This pattern is covered in SOACP Module 4: Fundamental SOA Analysis & Modeling with Services & Microservices.
For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.
This pattern is covered in SOACP Module 7: Advanced SOA Design & Architecture with Services & Microservices.
For more information regarding the SOA Certified Pofessional (SOACP) curriculum,
visit www.arcitura.com/soa.
This page contains excerpts from:
SOA Design Patterns by Thomas Erl
(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)
For more information about this book, visit www.arcitura.com/books.