Hey everyone,
A while back I made a comment on a thread on API versioning here:
https://community.apigee.com/questions/2271/api-versioning.html#comment-2570
Assuming we do want to version our API, and for sake of discussion, let's just assume we will do this through the URI. Do you think it's more appropriate to version across all APIs or per resource?
Here are the pros for each approach. Would be great to get your input:
Pro across all APIs:
Pros per resource:
You hem me in too much with your givens!
For the interdependency reasons you outline above I favor course grained versioning - meaning version all the resources in an API at once (even if only a subset have been modified). In this way you avoid the partial deprecation and interaction problems inherent in having fine grained resource versions.
As API designers we may need to confront this problem as platforms and practices evolve.
User | Count |
---|---|
7 | |
2 | |
2 | |
1 | |
1 |