#twitter poll: one repo or multiple repos as you build out a services architecture? Why?
-
-
@bascule agreed...trying to get a sense of that from the interwebs. :-) twitter research.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@mikegehard we use both at Square. Makes it easy to compare and contrast the approaches, kinda sucks in practice -
@bascule I bet. Any key takeaways or "it depends"? -
@mikegehard everything is terrible -
@mikegehard I would personally steer towards “microrepos” if the tooling were in place to make them work for you
End of conversation
New conversation -
-
-
@bascule@mikegehard fwiw, Perforce supports any repo model. Choice might depend on branch method (trunk/feature-based) & devops strategy? -
@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 :) - 2 more replies
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.