Endpoint versioning made simple
summary
A Spring Boot library implements a global version number so a single integer covers every endpoint, using a custom get-version-mapping annotation plus a WebMvc RequestMappingHandlerMapping extension to route requests. Live coding shows tests moving from 4 to 6 green checks, introduces a latestVersion constant to bump all endpoints at once, and supports ranged versions (e.g., 1..100). Published on Maven Central with a GitHub repo and ready-to-use examples.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:11Why version endpoints
- 4:20Problem with many versions
- 8:36Starting demo setup
- 11:49First solution attempt
- 16:05Introducing a library
- 21:28Using constants for versions
- 24:14Splitting version and resource
- 25:39Conclusion and Q&A
related talks
51mAPI Versioning In Spring Framework 7
59mFuture Proof with ASP.NET Core API Versioning
50mAPI Versioning for REST: In Real Life, How Do We Do It?
01h 00mModern API Versioning and Enterprise Ready AI Enablement with Spring Cloud Gateway
46mFrom Untested Spaghetti to Well-Rested Developers
40mFuture-Proofing Java: The Art of Crafting Resilient APIs
44mMastering Resilient Java API Design: From Principles to Practice
35mVersioning in a Microservice Architecture