Download now Free registration required
A major advantage of Service-Oriented Architectures (SOA) is composition and coordination of loosely coupled services. Because the development lifecycles of services and clients are de-coupled, multiple service versions have to be maintained to continue supporting older clients. Typically versions are managed within the SOA by updating service descriptions using conventions on version numbers and namespaces. This paper describes a method to automatically determine when two service descriptions are backward compatible. They then describe a case study to illustrate how they leveraged version compatibility information in a SOA environment and present initial performance overheads of doing so.
- Format: PDF
- Size: 331.6 KB