with the list of all important resources you will ever need.
Thank you for your article, Dr. Milan.
I would like to highlight that you consider RFC 7807 outdated in favor of RFC 9547.
Thank you, will fix!
About versioning of APIs.
In my opinion, versioning whether via URI, query parameter, or header, makes things complicated for the maintenance of the API.
Instead, using same URL and leveraging contract testing strategy, will help:
- Owners of the API to understand if some change they is breaking some user.
- Users will know when they have to adapt their client/s to the changes of the API
Sounds a bit drastic and there are occasions, like public APIs, were my proposal is not the best
undefined subscriptions will be displayed on your profile (edit)
Skip for now
For your security, we need to re-authenticate you.
Click the link we sent to , or click here to sign in.
Thank you for your article, Dr. Milan.
I would like to highlight that you consider RFC 7807 outdated in favor of RFC 9547.
Thank you, will fix!
About versioning of APIs.
In my opinion, versioning whether via URI, query parameter, or header, makes things complicated for the maintenance of the API.
Instead, using same URL and leveraging contract testing strategy, will help:
- Owners of the API to understand if some change they is breaking some user.
- Users will know when they have to adapt their client/s to the changes of the API
Sounds a bit drastic and there are occasions, like public APIs, were my proposal is not the best