Very, because building a service that is backwards compatible and / or has API guarantees is a lot of work. And a lot of these microservices share data model de

Very, because building a service that is backwards compatible and / or has API guarantees is a lot of work. And a lot of these microservices share data model definitions in one way or another, because it's perceived wasteful to try and keep them stable or duplicate them across API boundaries. Which in turn led to a push for monorepos, so these changes can be deployed across multiple services in one merge, and the multiple services deployed at once. In such an architecture, the people working on it acknowledge that using a network as a domain boundary is kinda inconvenient, but they spent a lot of effort on minimizing the inconvenience / overhead.