4 ms·
Still seems like caching is the only real issue. The complexity of dealing with headers seems easier than the complexity of routing constantly changing urls.
by jayd16 6y ago
Still seems like caching is the only real issue.
The complexity of dealing with headers seems easier than the complexity of routing constantly changing urls.
- iudqnolq 6y agoBlows 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?
- jayd16 6y agoMy 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/...) [1]https://stripe.com/docs/api/versioning https://stripe.com/docs/api/versioning