> That's the whole problem I'm talking about. Like I said, it forces you to reduce all these interfaces to lowest common denominator. I don’t know what you mea

> That's the whole problem I'm talking about. Like I said, it forces you to reduce all these interfaces to lowest common denominator. I don’t know what you mean by “lowest common denominator” or how “being forced to write good code” is inherently bad. There are lots of efficiencies to writing good code (easy to test, reuse, refactor, etc), not just writing microservices. > If you're just talking about each team having its own service, that's not what's usually meant by "microservices". That may not be the definition but it’s the principally cited advantage.