SOAPatterns.org

Overview
- Introduction
- History
- Acknowledgements
- Podcasts
- Candidate Patterns
- Forms
- Press Releases
- Resources
Compound Patterns
Design Patterns (alphabetical)
Design Patterns (by category)
- Foundational Inventory Patterns
- Logical Inventory Layer Patterns
- Inventory Centralization Patterns
- Inventory Implementation Patterns
- Inventory Governance Patterns
- Foundational Service Patterns
- Service Implementation Patterns
- Service Security Patterns
- Service Contract Design Patterns
- Legacy Encapsulation Patterns
- Service Governance Patterns
- Capability Composition Patterns
  - Capability Composition
  - Capability Recomposition
- Service Messaging Patterns
- Composition Implementation Patterns
- Service Interaction Security Patterns
- Transformation Patterns
- REST-inspired Patterns
Cloud Computing Patterns
Service Technology Specs
SOA School
- Home
- Matrix
- Certifications
- Courses
- Exams
- Self-Study Kits
- Workshops
- Licensing
- Online Store

Home > Design Patterns > Multi-Channel Endpoint

Multi-Channel Endpoint (Roy)

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, Contract Centralization, Data Format Transformation, Data Model Transformation, Legacy Wrapper, Process Abstraction, Protocol Bridging, Redundant Implementation

Related Service-Oriented Computing Goals

Increased Business and Technology Alignment, Increased Intrinsic Interoperability, Reduced IT Burden

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