API Versioning, Contracts & Testing
Evolving APIs without breaking consumers: semantic versioning, URI/header/media-type versioning, expand-contract, deprecation and Sunset, automated breaking-change detection, protobuf evolution, consumer-driven contracts with Pact, Testcontainers, and the strangler fig for monolith APIs.
About 90 minutes · 15 exam questions · 9 interview questions · 2 code labs
What you will learn
- What "breaking" means: compatibility vocabulary
- Semantic versioning for APIs
- Versioning strategies: URI, header, media type, dated versions
- Expand–contract (parallel change)
- Deprecation and sunset
- Detecting breaking changes automatically
- Protobuf field evolution rules
- Testing strategy for APIs: quadrant and pyramid
- Consumer-driven contract testing with Pact
- Component and integration tests with stubs and Testcontainers
- Strangler fig and facades: evolving a monolith's API
- Fitness functions and scenarios
Previous: API Design: REST, GraphQL & gRPC · Next: API Authentication, Authorization & Threat Modeling