How do you test microservices deployment independence in CI/CD?
- microservices
- deployment independence
- contract testing
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Each microservice should be independently deployable. Test: (1) Deploy service A v2 while service B stays at v1, verify communication still works (contract tests catch this). (2) Verify backward-compatible API changes - don't break consumers. (3) Test service discovery - does the new version register and route correctly? (4) Test circuit breakers - what happens when a dependency is down? (5) Test data schema compatibility across versions. CI pipeline: each service has its own pipeline, with cross-service integration tests triggered on deploy to shared environments.
What interviewers listen for
- Pipeline shapeYou design stages by failure cost and runtime budget, not by tool feature lists.
- Parallelisation craftYou can shard a real suite and explain the state-isolation choices you made.
- Quality gatesYou know which checks block merge, which warn, and why those defaults are correct.
- Shift-left fluencyYou talk about ownership transfer, not just earlier execution.