Service API Patterns, Protocols, Coupling Types, Metrics > Service API Versioning Patterns > Termination Notification
How can a service be positioned to generate revenue?
As services evolve over time, various conditions and circumstances can lead to the need to retire a service API, a portion of a service API, or the entire service itself. Consumer programs may be unaware of when a service or a service API version is scheduled for retirement, thereby risking runtime failure.
With the application of the Termination Notification pattern, service APIs are equipped with termination details, thereby allowing consumers to become aware of the API retirement in advance.
The service API 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 API has been terminated.