The presumption has it that a REST API should always be backward compatible with a service that is being exposed to such interfaces, be those external or internal clients. In this part of our tutorial we will go through the meaning of backward compatibility and what exactly it means.
Backward compatibility implies the connection within two clients that have no conflicts of compatibility between APIs. During the report of a service to another, if the clients are not corresponding with their updates or versions of the API, then issues might arise.
It is perceived that client implementation will take some time to catch up with service implementation, thus not breaking the existing version of the API, even though it has been the subject of an upgrade. The purpose of backward compatibility implies that older clients should still work fine with a new version of the same API. While the old client will miss out the new features of the upgraded...