Re:API versioning has no “right way” (2017)
by iudqnolq on Monday April 26, 2021 @11:30PM
(#26951669)
Blows up a smaller percentage of the time when you forget it is often worse.
How often are your APIs changing incompatibly anyway?
When they do changing the URL should dwarf next to changing the surrounding code to the new data model. If that's not the case then what was the point of the upgrade?
Re:API versioning has no “right way” (2017)
by jayd16 on Tuesday April 27, 2021 @12:03AM
(#26951875)
My point is its pretty trivial either way. With headers, you can use the stripe style[1] time stamp version headers that give you a clearer picture of exactly targeting an API as it was at any given time, instead of as it was stated in the url (ie .../vN/...)
The complexity of dealing with headers seems easier than the complexity of routing constantly changing urls.