I like a monorepo because as a component evolves, it tests its assumptions against the current state of the other components. In a way it forces a dialog betwee

I like a monorepo because as a component evolves, it tests its assumptions against the current state of the other components. In a way it forces a dialog between the owners of those components to understand each other's requirements. It's handy in cases where you tightly integrate and depend on each other's code. Like a more peer to peer relationship. MOST of the time, working at a company, this has been my experience. The other approach, multiple repos, I feel is best when there's a one-to-many relationship. Like a service with many customers. Or an open source project...