The article discusses the challenges and potential anti-patterns of versioning public web APIs, particularly critiquing the common practice of embedding version numbers in API paths (e.g., /api/v1) when using semantic versioning. The author raises concerns about coupling API routes with version numbers and the complications that arise when making breaking changes or developing new API versions. The piece invites discussion on API design best practices and versioning strategies.
Background
API versioning is a critical aspect of web development that ensures backward compatibility while allowing for evolution of services. The debate between different versioning strategies (path-based, header-based, query parameter-based) has been ongoing in the developer community.
- Source
- Lobsters
- Published
- May 29, 2026 at 01:44 PM
- Score
- 5.0 / 10