Pattern 39 / EDGE
Use this when evolving an API without breaking existing clients.
API Versioning fits when evolving an API without breaking existing clients. Mechanism: support multiple contract versions through URL, header, or media-type negotiation. Use it for public APIs and internal APIs with many independent consumers. The toll: old versions create maintenance burden and migration planning.
Public apis and internal apis with many independent consumers.
/v1/orders remains while /v2/orders adds fields and semantics.
Describe the pressure first, then the mechanism, then the cost. That keeps the design grounded.
Same pressure family