|
Hi, I am trying to gather some intelligence
around Versioning Problems in conjunction to SOA. In particular our SOA road is
primarily based on Web Services and interested to know how people are solving
the Versioning problem today. In terms of Versioning of Service I have
several questions in mind. Most organization start small on their SOA journey
with some initial pilot services. But soon these small services gain popularity
and now come the Versioning Issues. -Some clients want old API of service but
new clients want tweak to the same API. -Some clients want altogether
new/additional API to the service. -Some clients are interested few New API’s
but few old ones to. -Some clients would want same API but
would want to come over SSL secure rpc binding while others want non-secure doc
lit binding. Also, there are some -How to relay the new version availability?
-How many Endpoints to support for more or
less same business service? -How to manage-monitor multiple end points
for different versions? What are some of the best practices around
Versioning? How are people solving it today and what are the lessons learned
for future? Prashant Sarode Director SOA-Web Services Investors Bank & Trust Co.
SPONSORED LINKS
YAHOO! GROUPS LINKS
|
- [service-orientated-architecture] SOA Versioning Issues a... Sarode, Prashant
- Re: [service-orientated-architecture] SOA Versioning... Todd Biske
- [service-orientated-architecture] Re: SOA Versio... Prashant Sarode
- Re: [service-orientated-architecture] Re: SO... Todd Biske
- Re: [service-orientated-architecture] Re... Gregg Wonderly
