I think it boils down to two things that are not mutually exclusive: 1. Are you building a monolith? 2. What does your org chart look like? I work for a fairly

I think it boils down to two things that are not mutually exclusive: 1. Are you building a monolith? 2. What does your org chart look like? I work for a fairly large company where a monorepo doesn’t make a whole lot of sense because each team runs several services that get released or patched independently. If you have a large product composed of many components that need to function together as a cohesive whole, go ahead, use a monorepo.