SOA Patterns | Design Patterns | Cross-Domain Utility Layer


SOA Patterns > Inventory Implementation Patterns > Cross-Domain Utility Layer
Home > Design Patterns > Cross-Domain Utility Layer

Cross-Domain Utility Layer (Erl)

How can a service contract facilitate consumer programs with differing data exchange requirements?

Cross-Domain Utility Layer

Problem

While domain service inventories may be required for independent business governance, they can impose unnecessary redundancy within utility service layers.

Solution

A common utility service layer can be established, spanning two or more domain service inventories.

Application

A common set of utility services needs to be defined and standardized in coordination with service inventory owners.

Impacts

Increased effort is required to coordinate and govern a crossinventory utility service layer.

Architecture

Enterprise, Inventory

Cross-Domain Utility Layer: A cross-domain utility service layer establishes a set of common services that address broad, crosscutting concerns. Notice how a smaller quantity of utility services is required (compared to Figure 9.25) due to reduced redundancy.

A cross-domain utility service layer establishes a set of common services that address broad, crosscutting concerns. Notice how a smaller quantity of utility services is required (compared to Figure 9.25) due to reduced redundancy.


SOA Design Patterns

This page contains excerpts from:

SOA Design Patterns by Thomas Erl

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.arcitura.com/books.