Home > SOA Glossary > Service Governance Patterns

Service Governance Patterns

Service Governance Patterns represent the following set of patterns from the SOA Design Patterns catalog:

Compatible Change (Orchard, Riley)

How can a service contract be modified without impacting consumers?

Version Identification (Orchard, Riely)

How can consumers be made aware of service contract version information?

Termination Notification (Orchard, Riley)

How can the scheduled expiry of a service contract be communicated to consumer programs?

Service Refactoring (Erl)

How can a service be evolved without impacting existing consumers?

Service Decomposition (Erl)

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

Proxy Capability (Erl)

How can a service subject to decomposition continue to support consumers affected by the decomposition?

Decomposed Capability (Erl)

How can a service be designed to minimize the chances of capability logic deconstruction?

Distributed Capability (Erl)

How can a service preserve its functional context while also fulfilling special capability processing requirements?

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: