SOA Patterns > Service Governance Patterns > Termination Notification
Termination Notification (Orchard, Riley)
How can the scheduled expiry of a service contract be communicated to consumer programs?
Problem
Consumer programs may be unaware of when a service or a service contract version is scheduled for retirement, thereby risking runtime failure.
Solution
Service contracts can be designed to express termination information for programmatic and human consumption.
Application
Service contracts can be extended with ignorable policy assertions or supplemented with human-readable annotations.
Impacts
The syntax and conventions used to express termination information must be understood by service consumers in order for this information to be effectively used.
Principles
Architecture
Composition, Service
The service contract includes a standardized statement that communicates when it is scheduled for termination. As a result, the consumer does not attempt to invoke it after the contract has been terminated.
Related Patterns in This Catalog
Canonical Versioning, Compatible Change, Proxy Capability
Related Service-Oriented Computing Goals
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.
This page contains excerpts from:
Web Service Contract Design and Versioning for SOA
by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, Umit Yalcinalp, Canyang Kevin Liu, David Orchard, Andre Tost, James Pasley
For more information about this book, visit www.arcitura.com/books.