API changes should be Backward Compatible until all clients use the updated version
Whether you are in the middle of the development, or in the maintenance of a project involving several services, you should never introduce a “breaking” change in the way that systems interact. Instead, you should keep all clients working by providing an API with changes that are backward compatible, marking old usage as deprecated, so both ‘old’ and ’new’ clients can use the API without issues. Once all the clients use only the new API, then and only then you can remove the deprecated parts of the API....