Web Service Versioning

March 22nd, 2005

I’m attempting to put together a series of web service versioning patterns. So far I have:

  • No Version Pattern: Screw versioning!
  • Namespace Pattern: For each version change the namespace.
  • Version Parameter Pattern: Make the user submit the version of the service they’re accessing.
  • New Endpoint Pattern: For each version create a new endpoint.

Please read, add, change, comment, etc! Next up, I’ll be writing about how to implement these patterns using XFire.

One Response to “Web Service Versioning”

  1. Steve Currency Says:

    There is always the “named features” versioning. For each new incompatible feature, make all clients say that they are capable (and want to) use the new feature.

    Its more of a compatability way of doing it so that old clients can still use all new versions of the API.