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


Home > Foundational Inventory Patterns > Service Normalization

How can a service inventory avoid redundant service logic?  

Problem

When delivering services as part of a service inventory, there is a constant risk that services will be created with overlapping functional boundaries, making it difficult to enable wide-spread reuse.

Solution

The service inventory needs to be designed with an emphasis on service boundary alignment.

Application

Functional service boundaries are modeled as part of a formal analysis process and persist throughout inventory design and governance.

Impacts

Ensuring that service boundaries are
and remain well-aligned introduces
extra up-front analysis and
on-going governance effort.

Principles

Service Autonomy

Architecture

Inventory, Service
                
When services are delivered with complementary and well-aligned boundaries, normalization across the inventory is attained. Note also how the quantity of required services is reduced.
Audio Podcast
This pattern is discussed as part of the audio podcast:

Service Contract-Related SOA Design Patterns
 

Related Patterns in This Catalog

Capability Composition (Erl), Contract Centralization (Erl), Contract Denormalization (Erl), Domain Inventory (Erl), Enterprise Inventory (Erl), Entity Abstraction (Erl), Inventory Endpoint (Erl), Logic Centralization (Erl), Metadata Centralization (Erl), Process Abstraction (Erl), Policy Centralization (Erl), Proxy Capability (Erl), Schema Centralization (Erl), Service Decomposition (Erl), Service Refactoring (Erl), Utility Abstraction (Erl)


Related Service-Oriented Computing Goals

Increased Federation, Increased ROI, Reduced IT Burden


Related Publications

SOA Pattern of the Week: Service Normalization (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-2009
SOA Systems Inc.