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


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.

Principles

Standardized Service Contract, Service Loose Coupling

Architecture

Service
 
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.
Audio Podcast
This pattern is discussed as part of the audio podcast:

Service Contract-Related SOA Design Patterns
 

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)


Related Service-Oriented Computing Goals

Increased Vendor Diversification Options, Reduced IT Burden


Related Publications

SOA Pattern of the Week: Service Facade (InformIT)


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-2010
SOA Systems Inc.