Master SOA Design Pattern Catalog
|
|
|
|

Service Facade (Erl)

|

Home > Service Implementation Patterns > Service Facade
|
|
How can a service accommodate changes to its contract or
implementation while allowing the core service logic to evolve
independently?
|
|
|
|
|

Problem

The coupling of the core service logic to contracts and
implementation resources can inhibit its evolution and
negatively impact service consumers.
|
|

Solution

A service facade component is used to abstract a part of the
service architecture with negative coupling potential.
|
|

Application

A separate facade component is incorporated into the service
design.
|
 |
 |
 |

Impacts

The addition of the facade component introduces design effort
and performance overhead.
|
|
|
|
|
|
| |
|
|
Facade logic is placed in between the contract and the core service logic. This allows the core service logic to remain decoupled from the contract.
|
|
|
|
|

Related Patterns in This Catalog

Agnostic Sub-Controller (Erl),
Concurrent Contracts (Erl),
Contract Denormalization (Erl),
Data Format Transformation (Erl),
Decoupled Contract (Erl),
Distributed Capability (Erl),
Inventory Endpoint (Erl),
Partial Validation (Orchard, Riley),
Proxy Capability (Erl),
Service Decomposition (Erl),
Service Refactoring (Erl)
|

|
|
|

Related Patterns in Other Catalogs

Facade (Gamma, Helm, Johnson, Vlissides), Remote Facade (Fowler)
|

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