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

  1. What "breaking" means: compatibility vocabulary
  2. Semantic versioning for APIs
  3. Versioning strategies: URI, header, media type, dated versions
  4. Expand–contract (parallel change)
  5. Deprecation and sunset
  6. Detecting breaking changes automatically
  7. Protobuf field evolution rules
  8. Testing strategy for APIs: quadrant and pyramid
  9. Consumer-driven contract testing with Pact
  10. Component and integration tests with stubs and Testcontainers
  11. Strangler fig and facades: evolving a monolith's API
  12. Fitness functions and scenarios

Previous: API Design: REST, GraphQL & gRPC · Next: API Authentication, Authorization & Threat Modeling