D and microservices

[Laeeth Isharc via Digitalmars-d]

On Tuesday, 6 October 2015 at 19:31:20 UTC, Mengu wrote:
> a half of it is the buzz and other half of is not. remember 
> people talking about reactjs, go and rails being buzz? they 
> were the same. we have built an online payment gateway and we 
> are about to decouple our application and switch to 
> microservices architecture. we have an api, a dashboard, a 
> checkout page, mobile flow. we have to deal with accounting and 
> reporting as well. and there is no way that this application 
> will turn into a giant monolith. i don't want that. nobody 
> wants that. it will become something we cannot handle.

now a question for you.  do you wish you had built it from 
components from day one?  or do you see creating it as a blob to 
start with and then when the right divisions are clear factoring 
these out into micro-services as simply a natural part of the 
design process?  because you know much more by having started, 
and it's not so hard to refactor at this stage.

> another thing is whenever we do deployments we have to take 
> down the whole application and go offline

pretend I'm asking you before it was deployed in production...

> nobody suggests starting with microservices architecture 
> because you'll never know where things will lead you however 
> when it becomes a giant the suggestion is to use microservices.

some people do.  but I would have thought the point I made above 
is the real reason.  it doesn't take very long to write it that 
way from the beginning IFF you know what you want it to look like 
before you start.  and maybe you don't.  but I am interested in 
what your experience has been.