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


Home > Service Governance Patterns > Service Decomposition

How can the granularity of a service be increased subsequent to its implementation?  

Problem

Overly coarse-grained services can inhibit optimal composition design.

Solution

An already implemented coarse-grained service can be decomposed into two or more fine-grained services.

Application

The underlying service logic is restructured, and new service contracts are established. This pattern will likely require Proxy Capability to preserve the integrity of the original coarsegrained service contract.

Impacts

An increase in fine-grained services naturally leads to larger, more complex service composition designs.

Principles

Service Loose Coupling, Service Composability

Architecture

Service
 
The original, coarse-grained Invoice service is decomposed into three separate services, one of which remains associated with general invoice processing but only encapsulates a subset of the original capabilities.
Audio Podcast
This pattern is discussed as part of the audio podcast:

Service Governance Patterns for SOA
 

Related Patterns in This Catalog

Decomposed Capability (Erl), Decoupled Contract (Erl), Entity Abstraction (Erl), Proxy Capability (Erl), Service Facade (Erl), Service Normalization (Erl), Service Normalization (Erl), Service Refactoring (Erl), Utility Abstraction (Erl)


Related Service-Oriented Computing Goals

Increased Intrinsic Interoperability, Increased Federation, Reduced IT Burden


Related Publications

SOA Pattern of the Week: Service Decomposition (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.