Re: Microservices release question

re heading by keeping separate repo for each > microservice. > > Regards, > Adi > > -Original Message- > From: Myrle Krantz [mailto:mkra...@mifos.org] > Sent: 30 May 2016 23:43 > To: dev@fineract.incubator.apache.org > Subject: Re: Microservices release qu

RE: Microservices release question

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:

Re: Microservices release question

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 so

Re: Microservices release question

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 wrote: > On Tue, May 31, 2016 at 6:51 AM, Adi Raju > wrote: > > My thought would be to keep

Re: Microservices release question

On Tue, May 31, 2016 at 6:51 AM, Adi Raju 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.

RE: Microservices release question

My thought would be to keep core microservices as single repo and single release. Regards, Adi -Original Message- From: Myrle Krantz [mailto:mkra...@mifos.org] Sent: 31 May 2016 18:54 To: dev@fineract.incubator.apache.org Subject: Re: Microservices release question Adi, I like your

Re: Microservices release question

e are heading by keeping separate repo for each > microservice. > > Regards, > Adi > > -Original Message- > From: Myrle Krantz [mailto:mkra...@mifos.org] > Sent: 30 May 2016 23:43 > To: dev@fineract.incubator.apache.org > Subject: Re: Microservices release que

RE: Microservices release question

[mailto:mkra...@mifos.org] Sent: 30 May 2016 23:43 To: dev@fineract.incubator.apache.org Subject: Re: Microservices release question We should create a docker image and host it on docker hub for small organisations. These users would install docker, and run a single command to start the system

Re: Microservices release question

We should create a docker image and host it on docker hub for small organisations. These users would install docker, and run a single command to start the system. They wouldn't even have to download our compiled source directly; docker does that for you. We would need to figure out how to make i

Re: Microservices release question

Hi Myrle, Release process looks very interesting and same time highly confusing, I am wondering how small organisations or independent implementors will understand this process to carry out their implementations without much hurdles. Regards, Ashok On Mon, 30 May 2016 at 7:57 PM, Myrle Krantz w

Re: Microservices

In answer to Nayan's mail: Our shared end goal is not a beautiful architecture. Our shared goal is also not to make any particular company financially successful. Our goal is to make it possible for those people who today have no access to banking services to attain access to secure and timely s

RE: Microservices

the end user. Hope this helps a bit. Best, Markus .::YAGNI likes a DRY KISS::. > Date: Tue, 24 May 2016 19:41:28 -0700 > Subject: Re: Microservices > From: vish...@confluxtechnologies.com > To: dev@fineract.incubator.apache.org > > H

Re: Microservices

service. > > We will try to release some of the core features Myrle has talked about > pretty soon, so we can tackle some of the issues. For this we will keep > the implementation free from any new concept we are thinking about. > > Best, > > Markus > > .::YA

RE: Microservices

e of the issues. For this we will keep the implementation free from any new concept we are thinking about. Best, Markus .::YAGNI likes a DRY KISS::. > Date: Tue, 24 May 2016 10:23:56 +0100 > Subject: Re: Microservices > From: keithwood

Re: Microservices

Hi guys, First of all I think it's great that this discussion is now happening on the public mailing list. It will first of all generate a lot of good reading material for people looking to catch up on it later. To put it very blunt, I think the ultimate decision to move to a new model has indeed

Re: Microservices

Myrle, Sounds like Markus/you have been on this journey for a while already. Everything sounds great. Be very interested in seeing it come together. For that reason I think the sooner you are transparent about where the code is the better so the community can take a look also and help out where p

Re: Microservices

Hey Keith, I’ll start with the easy questions: * Have I done this before? Yes. But no woman is an island. I’m happy to have qualified advice. * Where will Markus and I be saving our work? We’ll send you a pointer once we feel it would be productive for others to look at it. Until we have a co

Re: Microservices

Mryle, >> Now please excuse me while I get back to just doing it. ; o) Ok sounds like decision made that yourself and Markus will be going ahead with this :) Can you let us know where you will be checking in the code so we in the community can follow along. Given your are going to go ahead with

Re: Microservices

Hi, I won't be able to write a complete answer. Nobody would read an e-mail that long. So I’m going to “nibble” at it bit by bit. Of the three approaches Keith lists, I favor the third approach "Re-imagine the fineract platform from ground up again (hope it solves the problems you see and doesn

Re: Microservices

Hi Mryle, Thanks for your detailed reply, I added my comments (please remember I am not involved in code base for sometime so might be missing alot) below but its a pretty long email so I summarise what I think here: The decision to move from one approach to developing a system to another is a bi

Re: Microservices

This is a big topic, and I’m trying to decide if I should chop it up into multiple threads. I’m going to leave it as one for now, since I detect a healthy scepticism about the question of whether we need to do this at all, and I don’t want to preclude that discussion. Here are some of the problem

Re: Microservices

Hi Myrle, First off, thanks for starting a conversation around this within the fineract dev community. I was wondering when this was going to come up. Rather than delving into the technicalities of what a microservice is and isnt I thought it would be good if the people proposing this could go in

Re: Microservices

Hi Myrle, microservices are indeed a nice architectural pattern with an exponentially growing adoption in the enterprise. It typically leverages some kind of a PaaS solution to be available for deployment. My current understanding is that your deployment model today is a traditional appserver. Are

Re: Microservices

Myrle, Microservices seems to be one of the big popular themes at OSCON this year - Drew and I are going to attend some sessions to get up to speed from a layperson's view :) http://conferences.oreilly.com/oscon/open-source-us/public/schedule/grid/public/2016-05-18