#apiversioning#rest#asp.netcore
169K subscribers • 11 videos on Hallway
Intermediate. Assumes working knowledge.
15K views1 year ago1 recommendation
Web developmentSoftware designAPI designSoftware architecture
Milan Jovanović demonstrates how to set up API versioning in ASP.NET Core before arguing why you should avoid versioning altogether.
Pragmatic REST APIs: milanjovanovic.tech/pragmatic-rest-apis Get the source code here: patreon.com/milanjovanovic Want to master Clean Architecture? Go here: bit.ly/3PupkOJ Want to unlock Modular Monoliths? Go here: bit.ly/3SXlzSt V1/V2 isn’t your default—evolution is. In this video, I first show how to wire up API Versioning in ASP.NET Core controllers, then I make the case for not versioning your APIs at all and using a clean change-management approach instead. You’ll learn - How to add ASP.Versioning for controllers, set a default version, choose readers (URL/header), and surface supported versions in response headers & OpenAPI. - Mapping endpoints to specific versions and marking older versions as deprecated. - Why multiple API paths (v1/v2) increase maintenance cost and complexity. - The API change management playbook: make additions optional, avoid removals/behavior changes, use content negotiation for new representations, and plan/communicate deprecations. - Practical migration tactics: introduce a new endpoint when business rules change; monitor client usage and retire legacy shapes safely. If this helped, subscribe for more .NET, EF Core, and pragmatic API design. What’s the hardest breaking change you’ve shipped—and how did you migrate clients? Your API Doesn’t Need Versions — Use Change Management Roy Fielding Says: Don’t Version APIs. Here’s Why. 📌 Resources: API Versioning in ASP.NET Core → milanjovanovic.tech/blog/api-versioning-in-aspnetcore The 5 Most Common REST API Design Mistakes (and How to Avoid Them) → milanjovanovic.tech/blog/the-5-most-common-rest-api-design-m… API Change Management → medium.com/good-api/api-change-management-2fe5bba32e9b 🧠 Full source code available to my Patreon supporters: patreon.com/milanjovanovic Check out my courses: milanjovanovic.tech/courses Read my Blog here: milanjovanovic.tech/blog Join my weekly .NET newsletter: milanjovanovic.tech Chapters Why we might need API Versioning Implementing API Versioning Why you shouldn't use API VersioningWhat people say. Recommended as a guide on how to handle API versioning and change management in ASP.NET Core.
u/iObsidianin r/dotnet • Recommends
On “Is this how would you do API version? l”