#twitter poll: one repo or multiple repos as you build out a services architecture? Why?
@dhruv_gupta @mikegehard well, the flipside is other SCMs (e.g. git) scale poorly to large monorepos, so prepare for Perforce lock-in
-
-
@bascule@mikegehard I see your point. Would you rather incur the cost of mini repos than be locked in? P4 does offer a git export. -
@dhruv_gupta@mikegehard I would rather be able to develop extensible distributed systems without having one repo as the source of truth ;) -
@bascule@mikegehard sure. Perforce also runs as dvcs now :) -
@dhruv_gupta@mikegehard yeah, Perforce in this discussion is an implementation detail -
@bascule@mikegehard an important detail given we were talking about scale. Scalability of vcs should not dictate repo model. -
@bascule@mikegehard scalability or lack there off :) -
@dhruv_gupta@mikegehard is there any VCS that scales to Google or Facebook-sized monorepos that isn’t Perforce? -
@bascule@mikegehard i would like to say "no". But i am biased.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.