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


Multi-Channel Endpoint (Roy)


Home > Legacy Encapsulation Patterns > Multi-Channel Endpoint
How can legacy logic fragmented and duplicated for different delivery channels be centrally consolidated?  

Problem

Legacy systems custom-built for specific delivery channels (mobile phone, desktop, kiosk, etc.) result in redundancy and application silos when multiple channels need to be supported, thereby making these systems burdensome to govern and difficult to federate.

Solution

An intermediary service is designed to encapsulate channelspecific legacy systems and expose a single standardized contract for multiple channel-specific consumers.

Application

The service established by this pattern will require significant processing and workflow logic to support multiple channels while also coordinating interaction with multiple backend legacy systems.
Impacts

The endpoint processing logic established by this pattern often introduces the need for infrastructure upgrades and orchestration-capable middleware and may turn into a performance bottleneck.

Principles

Service Loose Coupling, Service Reusability
Architecture

Service




The multi-channel service acts as the central contact point for different channel-based solutions (right) and legacy systems (left).


Related Patterns in This Catalog

Composition Autonomy (Erl), Contract Centralization (Erl), Data Format Transformation (Erl), Data Model Transformation (Erl), Legacy Wrapper (Erl, Roy), Process Abstraction (Erl), Protocol Bridging (Little, Rischbeck, Simon), Redundant Implementation (Erl)


Related Service-Oriented Computing Goals

Increased Intrinsic Interoperability, Increased Business and Technology Alignment, 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-2011
SOA Systems Inc.