SOA Patterns > Foundational Inventory Patterns > Enterprise Inventory
Enterprise Inventory (Erl)
How can services be delivered to maximize recomposition?
Problem
Delivering services independently via different project teams across an enterprise establishes a constant risk of producing inconsistent service and architecture implementations, compromising recomposition opportunities.
Solution
Services for multiple solutions can be designed for delivery within a standardized, enterprise-wide inventory architecture wherein they can be freely and repeatedly recomposed.
Application
The enterprise service inventory is ideally modeled in advance, and enterprise-wide standards are applied to services delivered by different project teams.
Impacts
Significant upfront analysis is required to define an enterprise inventory blueprint and numerous organizational impacts result from the subsequent governance requirements.
Architecture
Enterprise, Inventory
An enterprise service inventory establishes an enterprise-wide architectural boundary that promotes native interoperability and recomposition among all services.
Related Patterns in This Catalog
Canonical Protocol, Canonical Resources, Canonical Schema, Contract Centralization, Domain 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 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.