Slide 13
Slide 13 text
monorepo.tools: https://monorepo.tools/
“Not just “code colocation”
Consider a repository with several projects in it. We de
fi
nitely have “code colocation”, but if there
are no well de
fi
ned relationships among them, we would not call it a monorepo.
Likewise, if a repository contains a massive application without division and encapsulation of
discrete parts, it's just a big repo. You can give it a fancy name like "garganturepo," but we're
sorry to say, it's not a monorepo.
In fact, such a repo is prohibitively monolithic, which is often the
fi
rst thing that comes to mind
when people think of monorepos. Keep reading, and you'll see that a good monorepo is the
opposite of monolithic.
✋ Monorepo ≠ Monolith
A good monorepo is the opposite of monolithic! Read more about this and other misconceptions
in the article on “Misconceptions about Monorepos: Monorepo != Monolith”.
“
13