if it's not in the same repo, it means that the deployer can be updated and rolled out independently, and scale with its own resources. if it's in the same rep

if it's not in the same repo, it means that the deployer can be updated and rolled out independently, and scale with its own resources. if it's in the same repo, you add complexity -- now I have to ensure my deployment of two unrelated code bases don't collide, there's more cross-team conflicts, and I have to clone down a 200gb repo.