SOA Patterns > Inventory Implementation Patterns > Canonical Resources
Canonical Resources (Erl)
How can unnecessary infrastructure resource disparity be avoided?
Problem
Service implementations can unnecessarily introduce disparate infrastructure resources, thereby bloating the enterprise and resulting in increased governance burden.
Solution
The supporting infrastructure and architecture can be equipped with common resources and extensions that can be repeatedly utilized by different services.
Application
Enterprise design standards are defined to formalize the required use of standardized architectural resources.
Impacts
If this pattern leads to too much dependency on shared infrastructure resources, it can decrease the autonomy and mobility of services.
Principles
Architecture
Enterprise, Inventory
Services use the same standardized infrastructure resource for the same purpose. Note, however, that they do not share the same implementation of the resource.
Related Patterns in This Catalog
Atomic Service Transaction, Canonical Protocol, Compensating Service Transaction, Data Model Transformation, Domain Inventory, Enterprise Inventory, Intermediate Routing, Partial State Deferral, Process Centralization, Protocol Bridging, Reliable Messaging, Rules Centralization, Service Agent, Service Grid, State Repository
Related Service-Oriented Computing Goals
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.