0

I have a backend API that only has 1 version and is updated monthly.

There is an API management API that sits in front of this backend API. When the backend API is updated, I use the new swagger file from the backend API to update the API management API.

Should the API mangement API create a new version for every backend release? Considering the backend API only has 1 version, I think this would mean I would need to update all the previous versions of the API management API to keep it in sync with the new backend API. Is there any benefit to using versions here I am missing?

Blue
  • 38
  • 4
  • Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. – Community Mar 10 '22 at 14:27
  • 2
    You can refer to https://stackoverflow.com/questions/389169/best-practices-for-api-versioning , https://stackoverflow.com/questions/35280231/azure-api-management-and-api-versioning and https://social.msdn.microsoft.com/Forums/azure/en-US/193c102a-b3d3-42c1-8a00-54d36fd9edc9/apim-versioning-with-backend-api-versioning?forum=azureapimgmt – MadhurajVadde-MT Mar 11 '22 at 07:07

0 Answers0