I think sameera's suggestion is correct. If we use the product version as the version number, REST urls will change with every release. We should have a separate config file or another entry to define the version number and change the version numbers only if the backward compatibility breaks.
[1] http://www.ibm.com/support/knowledgecenter/SSRQ5X_8.5.6/com.ibm.wbpm.ref.doc/rest/calendar/index.htm Regards Nandika On Thu, May 5, 2016 at 12:42 PM, Hasitha Aravinda <[email protected]> wrote: > Some more questions > > On Thu, May 5, 2016 at 12:30 PM, Sameera Jayasoma <[email protected]> > wrote: > >> I believe its wrong to use the product version to version your micro >> services. >> >> You need to have different version for your microservices. e.g. starting >> from 1.0.0. If you don't change any of your microservices you shouldn't be >> changing these versions. >> > > According to Rest API guideline, it should be product version. isn't it ? > > Let's say we are using version from 1.0.0. > If we are going to do a modification > > to a microservice ( let's say foo 1.0) and new version is foo 1.1 Do we > need to maintain both versions to provide backward compatibility ? If so we > have to maintain two microservices: Foo 1.0 and Foo 1.1, because version is > a part of the path in microservice. > > eg: > @Path(" > /bps/bpmn/v > 1 > .0/ > foo > ") > , > @Path(" > /bps/bpmn/v > 1 > . > 1 > / > foo > ") > > Thanks, > Hasitha. > > >> On Thu, May 5, 2016 at 11:02 AM, Himasha Guruge <[email protected]> >> wrote: >> >>> Hi All, >>> >>> We have refactored our REST APIs by implementing Microservice interface. >>> According to the new REST guideline , we need to maintain the URL format >>> like below. For example, >>> >>> http://localhost:7777/bps/bpmn/v4.0/repository/deployments >>> >>> How are we going to maintain the product version updates with >>> microservices? If we are to maintain the product version with a parameter >>> been set from a config file, how can we achieve this? >>> >>> >>> Thanks, >>> Himasha Guruge >>> *Software Engineer* >>> WS*O2* *Inc.* >>> Mobile: +94 777459299 >>> [email protected] >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Sameera Jayasoma, >> Software Architect, >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> blog: http://blog.sameera.org >> twitter: https://twitter.com/sameerajayasoma >> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections >> Mobile: 0094776364456 >> >> Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > -- > Hasitha Aravinda, > Senior Software Engineer, > WSO2 Inc. > Email: [email protected] > Mobile : +94 718 210 200 > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Nandika Jayawardana WSO2 Inc ; http://wso2.com lean.enterprise.middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
