An exposed REST web service is consumed by various applications (mostly external applications).
Since we do not have control over external applications consuming our REST web service - changing an existing web service will often break existing consumer applications, there is a need for versioning control!
Learn from www.stripe.com and add the ability to publish multiple versions of a RESTful web service, where multiple versions of a web service is able to operate all at once.
Current work-around solution: clone eSpace, make changes to new eSpace, publish eSpace as a new version.
Since we do not have control over external applications consuming our REST web service - changing an existing web service will often break existing consumer applications, there is a need for versioning control!
Learn from www.stripe.com and add the ability to publish multiple versions of a RESTful web service, where multiple versions of a web service is able to operate all at once.
Current work-around solution: clone eSpace, make changes to new eSpace, publish eSpace as a new version.