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


Decoupled Contract (Erl)


Home > Service Contract Design Patterns > Decoupled Contract

How can a service express its capabilities independently of its implementation?  

Problem

For a service to be positioned as an effective enterprise resource, it must be equipped with a technical contract that exists independently from its implementation yet still in alignment with other services.

Solution

The service contract is physically decoupled from its implementation.

Application

A serviceˇ¦s technical interface is physically separated and subject to relevant service-orientation design principles.

Impacts

Service functionality is limited to the feature-set of the decoupled contract medium.

Principles

Standardized Service Contract, Service Loose Coupling

Architecture

Service




By decoupling the service contract, the service implementation can be evolved without directly impacting service consumers. This can increase the amount of refactoring opportunities and the range of potential consumer programs (and corresponding reuse).


Related Patterns in This Catalog

Concurrent Contracts (Erl), Contract Centralization (Erl), Contract Denormalization (Erl), Distributed Capability (Erl), Proxy Capability (Erl), Service Decomposition (Erl), Service Facade (Erl), Service Refactoring (Erl)


Related Patterns in Other Catalogs

Bridge (Gamma, Helm, Johnson, Vlissides), Separated Interface (Fowler)


Related Service-Oriented Computing Goals

Increased Intrinsic Interoperability, Increased Federation, 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.
Web Service Contract Design and Versioning for SOA This pattern is also discussed in the following title:

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

(ISBN: 013613517X, Hardcover, 826 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.