Skip to content
Sign in
Artwork for Architecture Corner
Architecture Corner · March 14 · 5 min

The Challenges of Evolving Your Service: API Versioning

Once you ship a public API, you've made a promise. Keeping it while still moving forward turns out to be harder than most teams expect. In this episode, we will cover: What qualifies as a backward-compatible change, and what doesn't Why does introducing a new API version cost more than just writing new code The real reason clients delay upgrades, and what you can do about it How to support multiple versions without duplicating your entire codebase The adapter pattern is a practical way to isolate version changes at the edges Know more here: https://medium.com/itnext/the-challenges-of-evolving-your-service-api-versioning-8008349a1154 Subscribe, for free, to the Architecture Corner Newsletter at https://architecturecorner.substack.com

0:00-5:25
Play in
Transcript file

transcript

No transcript — this publisher did not publish one.

show notes

Once you ship a public API, you've made a promise.

Keeping it while still moving forward turns out to be harder than most teams expect.

In this episode, we will cover:

  • What qualifies as a backward-compatible change, and what doesn't
  • Why does introducing a new API version cost more than just writing new code
  • The real reason clients delay upgrades, and what you can do about it
  • How to support multiple versions without duplicating your entire codebase
  • The adapter pattern is a practical way to isolate version changes at the edges

Know more here: https://medium.com/itnext/the-challenges-of-evolving-your-service-api-versioning-8008349a1154

Subscribe, for free, to the Architecture Corner Newsletter at https://architecturecorner.substack.com

more episodes

All episodes