[tovej]

This is just modularisation though. You can modularise without microservices. Microservices solve a scaling problem, not a design flexibility problem.

[iampims]

Micro services often solve _an organizational scaling_ problem, and are less frequently deployed for _performance scaling_.

[beaconstudios]

a monorepo also solves that same organisational scaling problem, but without introducing the artificial problem of basic function calls having to traverse the network, and having to keep tons of different services online and talking to each other.

[fennecfoxen]

Yeah, but it turns out people can’t actually write software right (or won’t) and this sort of network boundary is the only way to force them to write modular code, without the monolith collapsing into a tangled mess.

It’s really annoying.

[beaconstudios]

yes one of the biggest problems in software development is that most developers are bad at their jobs.

the solution, however, would be to hire a small number of really good developers and have code reviews run through them - hopefully teaching the more average developers how to code better in the process.

[emodendroket]

It’s so simple. You just need to devise the world’s first 100% predictive interview process

[beaconstudios]

I wish it were easy. The most important things to do are usually pretty hard, or they'd be done already.

[ABeeSea]

Since servers are ephemeral, any function call of note will need to traverse the network in some way anyway.

[beaconstudios]

that's true, but there's traversing 2 links for a simple client<->server<->database setup, or traversing dozens or even hundreds of links for a microservice architecture, adding tons of fragility for no unique benefit.

[asimpletune]

Well, there are legitimate benefits, it's just that few organizations are poised to understand/utilize them.