Roy Fielding Says: Don’t Version APIs. Here’s Why.

Pragmatic REST APIs: https://www.milanjovanovic.tech/pragm...
Get the source code here:   / milanjovanovic  
Want to master Clean Architecture? Go here: https://bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: https://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 → https://www.milanjovanovic.tech/blog/...
The 5 Most Common REST API Design Mistakes (and How to Avoid Them) → https://www.milanjovanovic.tech/blog/...
API Change Management →   / api-change-management  

🧠 Full source code available to my Patreon supporters:   / milanjovanovic  

Check out my courses:
https://www.milanjovanovic.tech/courses

Read my Blog here:
https://www.milanjovanovic.tech/blog

Join my weekly .NET newsletter:
https://www.milanjovanovic.tech

Chapters
0:00 Why we might need API Versioning
2:07 Implementing API Versioning
8:52 Why you shouldn't use API Versioning