> This only works for the simplest cases. If the two microservices must share data and direct calls (API calls) are not allowed
Actually, one assumption is that the microservices don't share data. Only API (Rest, SOAP, GraphQL, etc) calls are allowed. And the boundaries are created minimizing the coupling between microservices.
> While this let's you scale up teams, it's a huge overhead. So, unless you have over, let's say, 500 devs, it's not worth it.
As opposed to Monolith ? I think you will have problems collaborating in a Monolith at around 30 devs.
What I am opposing is the idea that you can have 30 devs and 50 microservices. Which I have seen in real life.
Actually, one assumption is that the microservices don't share data. Only API (Rest, SOAP, GraphQL, etc) calls are allowed. And the boundaries are created minimizing the coupling between microservices.
> While this let's you scale up teams, it's a huge overhead. So, unless you have over, let's say, 500 devs, it's not worth it.
As opposed to Monolith ? I think you will have problems collaborating in a Monolith at around 30 devs.
What I am opposing is the idea that you can have 30 devs and 50 microservices. Which I have seen in real life.