Information about how versioning of APIs is handled and how change is managed and communicated.
Versioning
Experiences
Change
Change is the one constant across the API landscape, and I watch teams struggle with it every single day. If you aren't actively managing and communicating change across versions, deprecations, and...
Provenance
I keep shining a light on provenance because nobody talks about it enough. Where did this data come from? How has this resource evolved? Without tracking the source and history of your API resource...
Stability
Stability is what consumers are really asking for when they evaluate your API. I see breaking changes, outages, and weird behavioral shifts erode trust fast. If people can't depend on your API for ...
Policies
Date-Based Versioning
Date-based versioning ties API changes to specific calendar dates. I see this approach working well for APIs where consumers want predictable release schedules they can plan around.
Semantic Versioning
Semantic versioning with major, minor, and patch numbers is the approach I see most often. It communicates the scope of change clearly -- breaking, feature, or fix.
Versioning
Versioning is how you communicate change to consumers. Whether you use semantic or date-based, being explicit about your versioning strategy and sticking to it builds confidence that change is mana...