SOA Patterns | Design Patterns | Canonical Protocol


SOA Patterns > Foundational Inventory Patterns > Canonical Protocol
Home > Design Patterns > Canonical Protocol

Canonical Protocol (Erl)

How can services be designed to avoid protocol bridging?

Canonical Protocol

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.

Architecture

Inventory, Service

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

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


SOA Design Patterns

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.