MonoRepo (vs ManyRepos)

MonoRepo is a single repository where all code resides.

It's also called a multi-package / multi app repositories.

• Single lint, build, test and release process.
• Easy to coordinate changes across modules.
• Single place to report issues.
• Easier to setup a development environment.
• Tests across modules are run together which finds bugs that touch multiple modules easier.

• Codebase looks more intimidating.
• Repo is bigger in size.

The vast majority of Google's software assets continues to be stored in a single, shared repository. See Why Google Stores Billions of Lines of Code in a Single Repository - The Google proprietary system that was built to store, version, and vend this codebase is code-named Piper. Google practices trunk-based development on top of the Piper source repository. The vast majority of Piper users work at the head

• https://speakerdeck.com/fabpot/a-monorepo-vs-manyrepos

monorepo

• https://github.com/facebook/react/tree/master/packages
• https://github.com/meteor/meteor/tree/devel/packages
• https://github.com/emberjs/ember.js/tree/master/packages

• submodule
• old git subtree split command:
  • splitsh automatically synchronize a monolithic repository to standalone repositories in real-time (old)

• http://danluu.com/monorepo/
• https://github.com/babel/babel/blob/master/doc/design/monorepo.md
• http://gregoryszorc.com/blog/2014/09/09/on-monolithic-repositories/
• http://gregoryszorc.com/blog/2015/02/17/lost-productivity-due-to-non-unified-repositories/
• Facebook:
  • https://www.youtube.com/watch?v=X0VH78ye4yY
  • https://code.facebook.com/posts/218678814984400/scaling-mercurial-at-facebook/
• https://www.digitalocean.com/company/blog/taming-your-go-dependencies/
• Twitter
• More …