Browse Teach Curate

API Versioning

Managing API change without breaking existing consumers: additive changes are safe under a tolerant-reader posture, while breaking changes require a new version (URL, header, or media type) and a deprecation window running both. In microservices you cannot force consumers to upgrade on your schedule.

jeremy Video

Designing Backward and Forward Compatible APIs

API compatibility theory defines two orthogonal properties: backward compatibility, where a newer version of an API continues to satisfy clients built against an older version, and forward compatibil…