No. Not at all. A monorepo with multiple back end projects might push all at different times. So what this means is that when designing new features across mult

No. Not at all. A monorepo with multiple back end projects might push all at different times. So what this means is that when designing new features across multiple services you need to design them with push safety in mind with a roll out plan to accomplish that. For example, you are updating service B to call new endpoint on service A. First you need to make service A endpoint available, and then make service B call service A. Just because everything exists in the same repo does not mean it all gets shoved out at once. The downside is that you can't just read the code and assume the running service is doing that, unless it's embedded in your build. Processes like automated updates and a forced update cadence (no running binaries over X days old) with proper canary/vetting before a full release allow a large org to still manage this complexity.