api-strategy
api-strategy copied to clipboard
Constraints on API Versioning
Perhaps, API Versioning constraints shall be introduced? Like COM "Interfaces must be immutable" or, at least, backward-compatible? In general, guidelines on API lifecycle may be needed.
I have created a draft for REST API Design Guidelines, containing a section on versioning. https://github.com/equinor/api-strategy/blob/rest-guidelines/docs/rest_guidelines.md
Feedback on the versioning section or anything else is appreciated, either in the PR or on email/Slack.