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 > Proxy Capability

Proxy Capability (Erl)

How can a service subject to decomposition continue to support consumers affected by the decomposition?

Problem

If an established service needs to be decomposed into multiple services, its contract and its existing consumers can be impacted.

Solution

The original service contract is preserved, even if underlying capability logic is separated, by turning the established capability definition into a proxy.

Application

Facade logic needs to be introduced to relay requests and responses between the proxy and newly located capabilities.

Impacts

The practical solution provided by this pattern results in a measure of service denormalization.

Principles

Service Loose Coupling

Architecture

Service

Listen to the podcasts that accompany this site

Proxy Capability: By preserving the existing capability and allowing it to act as a proxy for the relocated capability logic, existing consumers will be less impacted.

By preserving the existing capability and allowing it to act as a proxy for the relocated capability logic, existing consumers will be less impacted.

Related Patterns in This Catalog

Contract Denormalization, Decomposed Capability, Decoupled Contract, Distributed Capability, Service Decomposition, Service Façade, Service Normalization, Service Refactoring, Termination Notification

Related Service-Oriented Computing Goals

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.

This page contains excerpts from:

Web Service Contract Design and Versioning for SOA

by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, Umit Yalcinalp, Canyang Kevin Liu, David Orchard, Andre Tost, James Pasley

Foreword by David Chappell

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.

For more information about this book, visit www.servicetechbooks.com.