Should you keep separate versioning of your web-based interface and APIs?

Friday, July 4, 2014

Suppose you are developing a platform which has a web-based interface for its users and APIs for third-party developers. Something similar to Salesforce (or even Facebook).


Salesforce and Facebook, both platforms have normal web-based interface for its users and APIs for third party developers.


Ideally any API internally calls the same function which is being used by the web-based interface. For e.g. "Create a Project" button and "CreateProject" API calls the same "createProject()" function internally. So you can maintain same versioning for both as in most cases they are tightly integrated.


Now sometimes you add a feature which makes you increment the minor version of the web-based interface but since you are not implementing that feature in API, API version should remain as is.


How do you handle such cases? Should you keep separate versioning of your web-based interface and APIs for your platform?







http://ift.tt/1rsDoHJ