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 with
Page Numbers (PDF)
    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 Protocol (Erl)


Home > Foundational Inventory Patterns > Canonical Protocol

How can services be designed to avoid protocol bridging?  

Problem

Services that support different communication technologies compromise interoperability, limit the quantity of potential consumers, and introduce the need for undesirable protocol bridging measures.

Solution

The architecture establishes a single communications technology as the sole or primary medium by which services can interact.

Application

The communication protocols (including protocol versions) used within a service inventory boundary are standardized for all services.

Impacts

An inventory architecture in which communication protocols are standardized is subject to any
limitations imposed by the
communications technology.

Principles

Standardized Service Contract

Architecture

Inventory, Service




Though still delivered by different projects via different vendor platforms, these services conform to one centralized communications technology, making them technologically compatible.


Related Patterns in This Catalog

Canonical Resources (Erl), Canonical Schema (Erl), Cross-Domain Utility Layer (Erl), Data Model Transformation (Erl), Domain Inventory (Erl), Dual Protocols (Erl), Enterprise Inventory (Erl), Message Metadata (Erl), Protocol Bridging (Little, Rischbeck, Simon), Service Messaging (Erl)


Related Service-Oriented Computing Goals

Increased Intrinsic Interoperability, Increased Federation, Increased Organizational Agility, 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.