To monorepo or not to monorepo? That is the question!

With large tech companies such as Google famously touting the advantages of their monorepo strategy and other top tech companies talking about their equally impressive multirepo solutions, it can be difficult to decide which strategy is best for you and your team. Luckily, Gradle has plenty of experience helping organizations of all sizes and build tools through monorepo and multirepo transitions.

In this session, we hope to share our expertise no matter your build tool of choice. We’ll cover all the important decisions of both the monorepo and multirepo paths so that you can leave prepared for the path you choose and confident that you won’t end up abandoning the transition or stuck in the worst of both worlds.

These topics include how to:

work with and not against your organizational structure
select a new source code repository or modify an existing one
help geographically distributed teams
setup language and platform agnostic infrastructure
model the repository structure onto CI pipelines
factor performance and reliability tradeoffs into build tool choice