In our company, we have modularised most of the projects and are facing one of the biggest design hurdles: <code>one project per repository</code> or <code>multiple projects per repository</code> architecture. 
One of the biggest reasons of following <code>one project per repository</code> is being able to <code>release</code> individual components. 
What are your thoughts? What do you guys follow?

In our company, we have modularised most of the projects and are facing one of the biggest design hurdles: `one project per repository` or `multiple projects per repository` architecture. 

One of the biggest reasons of following `one project per repository` is being able to `release` individual components. 

What are your thoughts? What do you guys follow? 


Choosing between "one project per repository" vs "multiple projects per repository" architecture.

Product

Explore

Company

Blogs

Partner with us

Support

Comparisons

Comparisons