SOA Patterns > Foundational Inventory Patterns > Canonical Protocol
Canonical Protocol (Erl)
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
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, Canonical Schema, Cross-Domain Utility Layer, Data Model Transformation, Domain Inventory, Dual Protocols, Enterprise Inventory, Messaging Metadata, Protocol Bridging, Service Messaging
Related Service-Oriented Computing Goals
Increased Federation, Increased Intrinsic Interoperability, Increased Organizational Agility, Reduced IT Burden
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.