From the course: Advanced Azure Microservices with .NET for Developers

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Versioning

Versioning

- [Instructor] When building microservices, you should always strive to adopt a good versioning of strategy to avoid breaking changes at all costs when evolving your code. Generally speaking, additive changes are safe to implement, but what happens when you apply a breaking change in your code? Thanks to the versioning support in ASP.NET Core, you could easily expose different versions for your endpoints without worrying about breaking the current clients. For example, you could expose a V1 endpoint that receives requests from V1 clients. And also you could have an additional V2 endpoint that serves the V2 clients. With this in mind, it's easy to see how you could eventually deprecate your old code in favor of the most recent one. Remember that microservices should be autonomous and independently deployable. If you changed a microservice, you will deploy only that microservice and not the clients as well. In other…

Contents