I've never really explicitly thought of it this way, but you're exactly right. In a well-designed monolith (or early on in it's life), there should be a distinc

I've never really explicitly thought of it this way, but you're exactly right. In a well-designed monolith (or early on in it's life), there should be a distinct flow of dependencies. However, over time, with muliple devs coming and going, and requirements piling on, is that the dependencies turn into a ball of yarn. Having a physical deployment boundary might reduce this aspect of intertwined modules.