4 ms·
> it's not "just" a network rpc, even technically Except is is. Microservice doesn't mean distributed setup. For the first problem, yes service running in mult
by YetAnotherNick 3y ago
> it's not "just" a network rpc, even technically
Except is is. Microservice doesn't mean distributed setup. For the first problem, yes service running in multiple pods causes issues, but even monolith could face the same issue. Statefulset based microservices not only exists, but is a pretty common setup. Also I would even call multiple container on the same pod as microservice, which basically solves all of the problem.
There are many ways to solve second problem. Some folks create different API version. I prefer different deployment.
Last is a problem for monolith. I know of big companies where compile time is in order of an hour for monolith, even for small change.
- 0xbadcafebee 3y agoExcept it isn't, because a microservice requires an isolated dataset, API abstraction, documentation, versioning, consumer contract, dependency chain, complex release management. It's a radically different design because it forces you to develop the entire system differently to deal with very different abstractions, ways of working, expectations. A distributed monolith is simpler, but simultaneously more buggy than a centralized monolith.