Master SOA Design Pattern Catalog
|
|
|
|

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.
|
|
|
|
|
|
| |
|
|
|
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.
|
|
|
|
|

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)
|

|
|
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.
|
|