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/Microservices
Microserviceshard

How do you avoid breaking changes between services (API/contracts)?

Tags
#contracts#versioning#backward-compatibility
Back to categoryPractice quiz

Answer

Prefer backward-compatible changes (add optional fields, don’t remove/rename), version when needed, and validate contracts with consumer-driven tests. Deploy in an order that keeps old and new versions compatible during rollout.

Related questions

Microservices
REST vs gRPC for service-to-service calls: what are the key trade-offs?
#microservices#grpc#rest
Microservices
Consumer-driven contract tests: what are they and why use them?
#microservices#testing#contracts
Microservices
If services can’t share a DB, how do they share data?
#contracts
#events
#api