The original title is "Backward Compatibility: A Practitioner's Guide to Evolving APIs Without Breaking Clients"

Short summary

A practitioner's guide to evolving APIs without breaking clients, covering REST versioning strategies, GraphQL schema evolution, and mobile app compatibility. For REST, the author recommends URI path versioning for public APIs and header-based versioning for internal services, with concrete guidance on which changes are breaking vs non-breaking. GraphQL's field-selection model makes most additive changes safe by default, eliminating the need for versioned endpoints.

• •URI path versioning for public APIs; header-based for internal services
• •Non-breaking changes (adding fields, optional params) need no version bump
• •GraphQL schema evolution avoids versioning because clients only receive requested fields

Generated with AI, which can make mistakes.