U-Shaped Utility of Monorepos
https://matt-rickard.com/monorepos/
·
When you're organizing your code, you essentially have two choices – tracking changes in many smaller repositories or tracking changes in a single large repository. This is the age-old debate of "monorepos(itories) vs. multi/poly repos".
Monorepos have U-shaped utility. They are great for extremely small or extremely large organizations, and terrible for everything in between. Why's that?
Scaling with a monorepo. Google, Microsoft, Facebook, Uber, Airbnb, and Twitter all use monorepos. Why?