Hot to achieve Multiversioning/Backward compatability for Dotnet 8. APIs?

Nalavala, Harshavardhan 0

What is the effective way in achieving "Multiversioning, Versioning, Backward compatability" for Dotnet 8.0 APIs . These APIs are going to be deployed AKS cluster as microservices.

Anveshreddy Nimmala 3,540 Reputation points Microsoft Vendor

2024-06-04T06:13:06.76+00:00

Hello Nalavala, Harshavardhan,

Welcome to microsoft Q&A, thankyou for posting your query here.

To ensure backward compatibility and manage different versions of your API independently and provide different policies for different versions, you can use Azure API Management to create multiple versions of your API and manage them independently and to create new version of your API without breaking existing clients.

https://learn.microsoft.com/en-us/azure/api-management/api-management-versions

Hope this helps you.
Nalavala, Harshavardhan 0 Reputation points

2024-06-04T08:43:22.55+00:00

Hello @Anveshreddy Nimmala , I'm thinking of implementing versioning within APIs itself. But this might create code complexity and lot of testing. Is there any other way of doing it without using APIM? I can't go with APIM.

1 answer

Anveshreddy Nimmala 3,540 Reputation points Microsoft Vendor

2024-06-04T09:22:11.0933333+00:00

Hello Nalavala, Harshavardhan,

Configure Swagger to work with different versions of an API in .NET.

please find the below documentation if it is helpful anyway.

https://medium.com/@seldah/managing-multiple-versions-of-your-api-with-net-and-swagger-47b4143e8bf5

hope this helps you.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Hot to achieve Multiversioning/Backward compatability for Dotnet 8. APIs?

1 answer

Your answer