I was lucky enough to be in the right place, at the right time, to lead a group that scaled this approach across half a dozen different development teams. Fort

I was lucky enough to be in the right place, at the right time, to lead a group that scaled this approach across half a dozen different development teams. Fortunately everyone bought into the architecture, and respected the boundaries. Not everyone was senior, and not all the code was great, but we adopted the viewpoint that so long as the bad code is in the right spot (and not talking to things it shouldn’t) everything would be ok in the end. And it was. Half a dozen teams working in one codebase was definitely pushing it though, and the need to scale much beyond that would have definitely required some service-level compartmentalization to keep the ship from sinking, as you said. Even then, it would still be a far cry from the “microservices should be small enough to re-write in 2 weeks” approach.