Understanding the two different meanings of API versioning is a prerequisite to deciding how and when to use each. My aim is to bring some clarity and offer unequivocal practical advice.Ī significant part of the confusion around API versioning stems from the fact that the word “versioning” is used to describe at least two fundamentally different techniques, each with different uses and consequences. Here on the Apigee team at Google Cloud, we design, use and see a lot of APIs, and have developed some strong opinions about the right way to version them. With all this information, who’s an API developer to believe? (For some examples of those divergent views, take a look at this blog post and its bibliography and this interview with the author of the original REST dissertation). There's a lot of advice on the web about API versioning, much of it contradictory and inconclusive: One expert says to put version identifiers in HTTP headers, another expert insists on version identifiers in URL paths, and a third says that versioning of APIs is not necessary at all.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |