3 ms·

I'm curious as to why they went with the monorepo approach. This might sound really stupid, but couldn't you just have a seperate repo for each team/service? M

I'm curious as to why they went with the monorepo approach. This might sound really stupid, but couldn't you just have a seperate repo for each team/service? My approach is to shove everything in $GOPATH/src.

farslan 9y ago
Author here. The approach of a single repository for each project has its downsides, which I’ve tried to explain in the beginning of the slides already.