Then you have to start defining what you mean by "change". Some argue that if the change to a service affects the consumer, then you haven't changed the service but created a new one. i.e. that services should be immutable (like objects and interfaces)
We propose people manage change by catorgorising it as either being a new version, a revision or an implementation replacement. See http://cbdi.wikispaces.com/Service+Versioning for a precis of our guidance on the topic. Lawrence Wilkes (everware-cbdi.com, CBDIForum.com) --- In [email protected], Michael Poulin <m3pou...@...> wrote: > > While I agree with AW for the most part of the post, I would be VERY accurate > with the statement "In addition, if we want to change the implementation > itself, it will never affect the consumer at all". I know many examples (and > I wrote about them several times) where a change in the implementation > significantly affected consumer (not the consumer code directly involved into > service interface communication). SO is more than service invocation.
