sdfdfsfsdsdf

I have a team that doesn't communicate well and is generally dysfunctional in all ways imaginable.

Microservices isolate them quite literally and lets them work in peace and quiet.

The system as a whole is completely batshit crazy of course, but for some teams, this can turn an unworkable situation into "we might survive this" which is when push comes to shove all that matters.

It's called programming to an interface.

type ThingDoer interface { DoTheThingIDontCareHow() (result, error) }

func NewAmazingThingIMade(theThingINeedButIDontCareHowItDoesIt ThingDoer) { // You receive the superduper thing and dont care about it in any other way }

func (a *Amazing) DoSomeThing() (result, error) { return a.DoTheThingIDontCareHow() }

Nothing about "monoliths" prevents or hampers this development style. Once someone decides to do the Thing in another fashion, they are free to do so and you wouldn't have to change a thing.

All problems you experience are organizational, not technical. It's psychology we should be studying, not computer science.

Edit: In fact you introduced a network boundary which can fundamentally only complicate matters, not make them simpler.