Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Architecture
Architecturehard

API versioning — when do you version and what are two common strategies?

Tags
#api-versioning#backward-compatibility#rest
Back to categoryPractice quiz

Answer

Version when you introduce breaking changes you can’t make backward compatible. Common strategies: version in the URL (`/v2/...`) or via headers/content negotiation. Prefer backward-compatible changes when possible (add optional fields).

Related questions

Architecture
Event schema evolution — how do you avoid breaking consumers?
#events#schema-evolution#backward-compatibility
Architecture
REST vs GraphQL?
#api#rest#graphql
Spring
`@RestController` vs `@Controller`: what’s the difference?
#spring#mvc#controller
Microservices
REST vs gRPC for service-to-service calls: what are the key trade-offs?
#microservices#grpc#rest
Spring
`@RequestParam` vs `@PathVariable` — when do you use which?
#spring-mvc#requestparam#pathvariable
Microservices
How do you avoid breaking changes between services (API/contracts)?
#contracts#versioning#backward-compatibility