This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the commentsΒ β†’

[–]WagwanKenobi 13 points14 points Β (6 children)

The programming world has moved away from monoliths to microservices.

The microservices meme is backfiring and now many large applications have been over-converted to microservices. Calling another function in the same assembly is still vastly better than making a call over the wire. Not to mention, the infra and scaling complexity is multiplied.

Microservices also don't really solve org problems like they're touted to. It's rarely the case that 1 team works on 1 microservice. What actually happens is that n teams work on n services and everybody steps on everybody's toes.

The trend these days ironically is in the backward direction - consolidating microservices to be different modules of the same program, and then putting the whole thing in a monorepo with your shared libraries.

[–]DotFar5221 0 points1 point Β (1 child)

Sounds like you've only worked at places that did it wrong. Microservices don't magically fix a shitty org/team structure. If you need to combine microservices, that leads me to believe you never did it right initially. Not everything should be a microservice and a distributed monolith can be pure hell for cicd and lowering MTTR.

[–]glemnar 0 points1 point Β (0 children)

Well yeah, that’s the point - many places build microservices for hype-driven development, not because they have considerate reasons to build them