3 ms·
The industry is heading this direction but the problem with microservices is that they're frequently chosen prematurely / misused / cargo-culted, chosen as a pa
by tedmiston 9y ago
The industry is heading this direction but the problem with microservices is that they're frequently chosen prematurely / misused / cargo-culted, chosen as a panacea without considering their tradeoffs and communication overhead.
Most of it really just goes back to the fallacies of distributed computing. A lot of people don't think about ways that microservices, by way of being decoupled, can be less efficient or fail between components, the network, etc where a monolith can't… until after they're built (or never).
The majority of apps in the world don't reach the point where the benefits of microservices outweigh their tradeoffs. Or they choose microservices to fix a problem that is really that the app is not decomposed well into clean modules and components. Even the creator of microservices says to go monolith first (https://martinfowler.com/bliki/MonolithFirst.html https://martinfowler.com/bliki/MonolithFirst.html).