> If there is an issue with a single deploy, it stops the whole company from shipping changes.
I don't agree with this characterization. There is a way to 'lock' an entire repo from deploys, but it's not very frequently used. Single-service deploy blocks are common (if an autodeploy fails, or a team is aware of an issue and actively fixing it).
Stripe uses Bazel heavily.
> there was a project well underway to pull some core product / business functions into specific repos
This quote from the post is also not true to my knowledge: new repos are not allowed and teams are actively working to migrate small repos into the monorepo(s).
I don't agree with this characterization. There is a way to 'lock' an entire repo from deploys, but it's not very frequently used. Single-service deploy blocks are common (if an autodeploy fails, or a team is aware of an issue and actively fixing it).
Stripe uses Bazel heavily.
> there was a project well underway to pull some core product / business functions into specific repos
This quote from the post is also not true to my knowledge: new repos are not allowed and teams are actively working to migrate small repos into the monorepo(s).