News for hackers. Stuff that matters.

A comment on Should that be a microservice? Factors to keep in mind. Parent comment

Re:Should that be a microservice? Factors to keep in mind by dragonwriter on Sunday April 21, 2019 @10:01AM (#19712099)
> Almost always a monolithic with some SOA and clear domain boundaries is going to work better for static/slow growth teams.

If it has “some SOA and clear domain boundaries” its not a monolith, even if it isn't decomposed so far as to be microservices.

“Right-sized services” isn't a catchy meme-spreading label, but it's probably the synthesis pointed to by microservices as the antithesis to monoliths.

[ Parent | on HN ]
Re:Should that be a microservice? Factors to keep in mind by lugg on Sunday April 21, 2019 @12:12PM (#19712741)
Monolithic just means it can carry out all it's required functionality alone, i.e. it's [major] dependencies are internalized.

It doesn't say anything about not being able to be broken into modularized sections, services, or domain boundaries.

Neither does it reject any setups where satellite systems, micro or otherwise make use of the monolith programmatically or otherwise, hell it's kond of part of the definition of a monolith that it has multiple access points (i.e. cli, sdk, rest, rpc, events.)

[ Parent | on HN ]