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 Refactoring (Erl)


Home > Service Governance Patterns > Service Refactoring

How can a service be evolved without impacting existing consumers?  

Problem

The logic or implementation technology of a service may become outdated or inadequate over time, but the service has become too entrenched to be replaced.

Solution

The service contract is preserved to maintain existing consumer dependencies, but the underlying service logic and/or implementation are refactored.

Application

Service logic and implementation technology are gradually improved or upgraded but must undergo additional testing.

Impacts

This pattern introduces governance effort as well as risk associated with potentially negative side-effects introduced by new logic or technology.

Principles

Standardized Service Contract, Service Loose Coupling, Service Abstraction

Architecture

Service




All parts of a service architecture abstracted by its contract can potentially be refactored without compromising existing consumer relationships. The service contract and the remaining, externally facing message processing agents (red) are not affected by the refactoring effort.


Related Patterns in This Catalog

Concurrent Contracts (Erl), Contract Centralization (Erl), Decoupled Contract (Erl), Distributed Capability (Erl), Proxy Capability (Erl), Service Decomposition (Erl), Service Facade (Erl), Service Normalization (Erl), Validation Abstraction (Erl)


Related Service-Oriented Computing Goals

Increased Vendor Diversification Options, Increased Organizational Agility, 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.
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.