A lot of the benefit that comes from this code storage method doesn't really seem like the best solution. The presenter in the video linked in this thread that

A lot of the benefit that comes from this code storage method doesn't really seem like the best solution. The presenter in the video linked in this thread that this is very advantageous due to cross dependencies. I don't think that this is the correct way to handle a cross dependency. I'd much rather handle it by abstracting your subset of the problem into another repository. Have some features that two applications need to share? That means you're creating a library in my mind. This is much better suited for something like git as you can very simply use sub-modules to your advantage. Hell, you can even model this monolithic system within that abstracted system. Create one giant repository called "libraries" or "modules" that just includes all of the other sub-modules you need to refer to. You now have access to absolutely everything you need within the google internal code base. You can now also take advantage of having a master test system to put overarching quality control on everything. This can be done automatically. Pull the git repo, update all the sub-modules, run you test platform. I'd say that's a better way to handle it. Creating simple front end APIs for all of the functionality you need to be shared.