Versioning
The most common way to manage changes of an API is to use versioning. Using versioning is basically a way that you can let the developers of the clients of the API know, right from the beginning, that there might be changes in the API that will be backward incompatible as the business model evolves. However, this doesn't mean that you cannot add new APIs to the same version. In fact, you don't have to change the version as long as you do not create backward incompatibility issues in your API. So, versioning is not the cause of backward incompatibilities. On the contrary, it is a way to manage that issue. It is often a lack of consideration during the API design or the changes of the application's business models that introduce ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access