Being fair, for many of the things that it is worth using a microservice for, you should already have some sort of dominant factor to the call that would more t

Being fair, for many of the things that it is worth using a microservice for, you should already have some sort of dominant factor to the call that would more than justify the added latency of the remote call. Be it a database read/write or some other heavy calculation. Granted, this is exacerbated when architectures don't make a good division between control/compute/data planes. Control plane, which is exposed to users, should almost certainly be limited to a single (or handful, at most) microservice calls. Preferably to the fastest storage mechanism that you have, such that what latency it does add is minimized entirely.