One thing that works well in "monorepo" is that API specs are in the same repo for "queries" and "answers". In a multi-repo world, you have three distinct possi

One thing that works well in "monorepo" is that API specs are in the same repo for "queries" and "answers". In a multi-repo world, you have three distinct possibilities, the API spec goes in the "answers" repo (this is pretty natural, but requires a build system that triggers "queries" rebuilds/retests on changes), the API spec goes in a dedicated repo, or the API spec goes into one of the "queries" repos. This ordering is probably in order from "most" to "least" obvious, and I don't have an answer for what the correct solution is. Most probably "separate repo", making the interface not privileged to either side of the "interface barrier". FWIW, building at Google when at a 8h offset from Pacific Time worked fine, indicating that part of the problem is "does your repo/build solution scale to tens of thousands of simultaneous users".