For software developers, versioning is such an engrained part of what we do that we naturally think it applies to all sorts of software, regardless of how it is used. For long-lived, distributed systems, versioning takes a different form.

This talk explains how instead of a versioning strategy for your web API, you should have a change strategy. The talk goes through what this means in practice, a set of rules you should follow to ensure that you don't break clients all the while allowing your API to change and evolve with minimum code debt.