API Versioning In Spring Framework 7
summary
Spring Framework 7 adds first-class API versioning: server-side config declares where versions live (header, query, path-segment and header strategies or a pluggable resolver), request mappings carry version annotations with support for semantic-version parsing, baseline ranges (highest compatible below a requested version), required/default versions, and custom parsers (example: date→version mapping like Microsoft’s grouping). Client libraries (WebClient, RestTemplate/Rest client, HTTP services) insert versions automatically and testing helpers include WebTestClient and MockMvcTester integrations. Deprecation header support is discussed but not yet implemented.
AI-written summary · about
chapters (18)
- 0:00API versioning intro
- 1:08Why API versioning matters
- 3:16Roy Fielding’s view
- 8:39Path vs header versioning
- 16:52Industry versioning practices
- 17:12Spring 7 versioning support
- 18:58Demo: Versioned endpoints
- 25:21Demo: Version ranges
- 29:31Demo: Path-based versioning
- 32:22Semantic versions in Spring
- 33:54Custom date-based parsing
- 35:42Advanced versioning customizations
- 37:06Client-side versioning
- 40:36Testing versioned APIs
- 44:50Reference documentation and resources
- 45:17Q&A: Deprecation headers
- 46:44Q&A: Type safety
- 49:56Q&A: OpenAPI docs
related talks
27mEndpoint versioning made simple
50mAPI Versioning for REST: In Real Life, How Do We Do It?
59mFuture Proof with ASP.NET Core API Versioning
01h 00mModern API Versioning and Enterprise Ready AI Enablement with Spring Cloud Gateway
25mHow to Approach Retroactive API Versioning
48mSavoir vivre for applications - a few words on API versioning
53mAPI Standards 2.0
35mVersioning in a Microservice Architecture