| Title: |
Service Versioning |
| Author: |
John Dodd and Lawrence Wilkes |
| Publication Date: |
16 February 2006 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
We are frequently asked to provide advice on “service versioning”, and explain how to handle upgrades to software services. Service versioning is not a new problem: it has been a consistent challenge with different technical approaches to distributed computing such as CORBA, COM and now Web Services. This report proposes that three main categories of service release should be recognized, and that the release procedures will need to be different for each. |
| Backgrounder: |
Web Services bring no new technical solution to the challenge of Service Versioning. Moreover, as SOA is not predicated on Web Services, an enterprise SOA may comprise Services and Service Automation Units implemented in many different technologies. Consequently, organizations first need to set out their overall approach to versioning that in a technology-neutral manner.
In a prior report we outlined the basic model for the Service Lifecycle. In it, we suggested that “versioned” is not a separate state for a Service, but rather that each release is viewed as a separate object which passes though the same service lifecycle as earlier versions. This report builds on the three kinds of service release that were introduced in that report. |
| Report Size: |
9 pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home