It still has all the other disadvantages of remote services, like consistency problems (everybody always assumes that RPC calls are as reliable as 2 phase commit, and they&#x27;re not), more and more complex code that&#x27;s harder to change, less flexibility on all fronts except for the one, ...<p>Things like distribution are a tradeoff, an optimization : you should never split a monolithic application into 2 communicating parts until you have good reason to do so.<p>A monolithic system executing a given function is pretty much guaranteed to be simpler than a distributed system doing the same function.<p>A small amount of microservices is easier on the guy doing ops work for the system, because they can be individually replaced, upgraded or changed (IF the developers put in the constant amounts of efforts needed to make that possible. Every release should be able to deal with past versions of everything it talks to). These guys are also usually the ones doing load balancing and the like, so bonus points for being able to spread them over the network.<p>Of course, numbers of microservices always grow, and grow, and grow some more. Soon it&#x27;s not easier anymore on the ops guy, and becomes a constant drag on progress for everyone.