Home > SOA Glossary > Common Compound Design Patterns

Common Compound Design Patterns

Common Compound Design Patterns Patterns represent the following set of patterns from the SOA Design Patterns catalog:

Orchestration (Erl, Loesgen)

Co-existent application of Process Abstraction, State Repository, Process Centralization, and Compensating Service Transaction, can can be further extended with Atomic Service Transaction, Rules Centralization, and Data Model Transformation.

Enterprise Service Bus (Erl, Little, Rischbeck, Simon)

Co-existent application of Asynchronous Queuing, Intermediate Routing, and the Service Broker compound pattern and can be further extended via Reliable Messaging, Policy Centralization, Rules Centralization, and Event-Driven Messaging.

Service Broker (Little, Rischbeck, Simon)

Co-existent application of Data Model Transformation, Data Format Transformation, and Protocol Bridging.

Canonical Schema Bus (Utschig, Maier, Trops, Normann, Winterberg, Erl)

Co-existent application of Enterprise Service Bus, Decoupled Contract, Contract Centralization, and Canonical Schema.

Official Endpoint (Erl)

Joint application of Logic Centralization and Contract Centralization.

Federated Endpoint Layer (Erl)

Joint application of Official Endpoint, Service Normalization, Canonical Protocol, Canonical Schema, and Canonical Expression.

Three-Layer Inventory (Erl)

Joint application of Utility Abstraction, Entity Abstraction, and Process Abstraction.

These patterns were first printed in the SOA Design Patterns book and summarized versions of the patterns are published at the SOA Patterns community patterns site.

See Also: