Return to Home Page
Overview
    History
    Acknowledgements
    Podcasts
    Notification Form
    Feedback Form
    Press Release #1
    Press Release #2
    Press Release #3

Master SOA Design
Pattern Catalog
    Master Pattern List (alphabetical)
    Master Pattern List (by category)
    Master Pattern List (Text)
    Pattern Notation
    Pattern Profiles
    Symbol Legend
    Pattern Contribution Form

SOA Candidate Patterns
    SOA Patterns Review Committee
    Candidate Patterns Overview
    Candidate Patterns List
    Candidate Pattern Contribution Form
    Candidate Pattern
Feedback Form
    SOA Pattern Template

Design Pattern Basics
    What's a Design Pattern?
    What's a Design Pattern Language?
    What's a Compound Pattern?

Supplemental
    SOA Patterns and Application Technologies
    SOA Design Patterns Historical Influences
    SOA Design Patterns and Design Principles
    SOA Design Patterns and Design Granularity
    Legal

Resources
    Design Patterns Publications
    Reference Posters
    SOAPrinciples.com
    WhatIsSOA.com
    SOA Visio Stencil


Canonical Resources (Erl)


Home > Inventory Implementataion Patterns > Canonical Resources
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

Service Autonomy

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 (Erl), Canonical Protocol (Erl), Compensating Transaction (Utschig, Maier, Trops, Normann, Winterberg, Loesgen, Little), Data Model Transformation (Erl), Domain Inventory (Erl), Enterprise Inventory (Erl), Intermediate Routing (Little, Rischbeck, Simon), Partial State Deferral (Erl), Process Centralization (Erl), Protocol Bridging (Little, Rischbeck, Simon), Reliable Messaging (Little, Rischbeck, Simon), Rules Centralization (Erl), Service Agent (Erl), Service Grid (Chappell), State Repository (Erl)


Related Service-Oriented Computing Goals

Increased Vendor Diversification Options, Reduced IT Burden


SOA Design Patterns 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.
The Prentice Hall Service-Oriented Computing Series from Thomas Erl
Home    SOA Books    SOA Magazine    What is SOA?    SOA Principles    SOASchool.com    SOA Glossary Copyright © 2007-2009
SOA Systems Inc.