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


Protocol Bridging

(Little, Rischbeck, Simon)



Home > Transformation Patterns > Protocol Bridging

How can a service exchange data with consumers that use different communication protocols?  

Problem

Services using different communication protocols or different versions of the same protocol cannot exchange data.

Solution

Bridging logic is introduced to enable communication between different communication protocols by dynamically converting one protocol to another at runtime.

Application

Instead of connecting directly to each other, consumer programs and services connect to a broker, which provides bridging logic that carries out the protocol conversion.

Impacts

Significant performance overhead can be imposed by bridging technologies, and their use can limit or eliminate the ability to incorporate reliability and transaction features.

Principles

Standardized Service Contract, Service Composability

Architecture

Inventory, Composition




The consumer programs interact with a middle-tier broker that provides protocol bridging features. Separate protocol adapters are used to translate the two incompatible protocols to the required SOAP version 1.2 over HTTP. The broker then transmits the messages to the service on behalf of the consumers.


Related Patterns in This Catalog

Canonical Protocol (Erl), Canonical Resources (Erl), Data Format Transformation (Erl), Data Model Transformation (Erl), Dual Protocols (Erl), File Gateway (Roy), Inventory Endpoint (Erl), Legacy Wrapper (Erl, Roy), Multi-Channel Endpoint (Roy), Service Agent (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.