|
|
Master SOA Design Pattern Catalog
|
|
|
|

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.
|
|
|
|
|
|


|
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)
|

|
|
|
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.
|
|