Grokking Modern API Design Interview
Vote

0% completed

​

Versioning and Backward Compatibility

An interviewer asks:

"How would you version this API?"

The usual answer begins too late: "I would put v1 in the URL."

The first question is:

Does the proposed change break existing callers?

Most useful changes do not need a new major version. A version is a migration tool for a genuinely incompatible contract, not a label changed whenever the implementation ships.

1. Compatible and Breaking Changes

Adding risk_level to a payment response is compatible when old callers ignore it

.....

.....

.....

Like the course? Get enrolled and start learning!