[coldtea]

>Surprising this has been written in 2017. It looks like java written a decade ago.

Because good architecture has somehow evolved?

>This can be a kind of organizational solution much like microservices to separate concerns.

This is orthogonal to microservices. And microservices aint but one model of creating applications, not "THE 2017 model".

[threeseed]

> Because good architecture has somehow evolved?

Of course. Every year gives us greater insight into what approaches work and don't work. Which is why we have seen Java technologies like EJB, JCA, JTA, OSGI, JSP etc generally fall by the wayside in favour of less convoluted and less architecturally heavy approaches.

> And microservices aint but one model of creating applications, not "THE 2017 model".

Microservices are unquestionably the defacto standard for most larger software development projects. Especially since they are intrinsically linked to the containerisation deployment approach which is a modern day concept.

[heartbreak]

> Microservices are unquestionably the defacto standard

There's a wide world of software out there that you have yet to explore.

[coldtea]

>Microservices are unquestionably the defacto standard for most larger software development projects.

In the HN echo chamber maybe -- but not sure even there.

[hamilyon2]

I am very intetested. What makes you think that microservices is current standard? Is there a peer-reviwed study?

[thehardsphere]

I agreed with the first part of your answer a lot more than the second part.