Hey all, Just to be clear, I could live with repos that collect multiple services to bundle them in a release, but I don't really like it. ; o)
Now let's start to find a solution. For me it is hard to decide what the core functionalities of the new approach are, given we also design it in a way that you can swap out any service with your own implementation. A possible solution could be to 'group' services like Spring is doing it. Providing a framework repository with services that are crucial to the overall product. (As mentioned, as of now I can't tell what the content will look like.) All additional services are grouped based on their purpose and following a release train approach where dependencies to the framework are tied to a specific train, and only minor releases will be recognized within one train. You can look at the Spring Framework, Spring Data, and Spring Boot to see how this is working. In this way we could provide multiple artifacts that have a clear list of dependencies built in. Best, Markus .::YAGNI likes a DRY KISS::. ---------------------------------------- > Date: Wed, 1 Jun 2016 09:51:54 +0200 > Subject: Re: Microservices release question > From: mkra...@mifos.org > To: dev@fineract.incubator.apache.org > > Hi Nayan, > > Good question. I would expect it to consist of the tenant provisioning > service, the security service, and the supporting libraries for the command > bus, and a couple of other shared functionality tidbits. > > As to Adi's wish to keep them together in one repository: it's not my > preferred solution, but I see several arguments for it and I can live with > it if that's what you guys prefer. > > Greets, > Myrle > > > *Myrle Krantz* > Solutions Architect > RɅĐɅЯ, The Mifos Initiative > mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org > <http://facebook.com/mifos> <http://www.twitter.com/mifos> > > > On Wed, Jun 1, 2016 at 6:51 AM, Nayan Ambali <nayan.amb...@gmail.com> wrote: > >> Adi, Myrle, >> >> When you say core, what core is constituted of? >> >> Thanks >> Nayan Ambali >> >> >> >> Thanks and Regards, >> Nayan Ambali >> +91 9591996042 >> skype: nayangambali >> >> On Wed, Jun 1, 2016 at 12:28 AM, Roman Shaposhnik <ro...@shaposhnik.org> >> wrote: >> >>> On Tue, May 31, 2016 at 6:51 AM, Adi Raju >>> <adi.r...@confluxtechnologies.com> wrote: >>>> My thought would be to keep core microservices as single repo and >> single >>> release. >>> >>> FWIW: that'd be my preference as well. >>> >>> Thanks, >>> Roman. >>> >>
