> In addition, Stripe’s monorepo was (to our knowledge) the largest Ruby codebase in existence
Bigger than shoppify's?
Bigger than shoppify's?
Also on a headcount level, Google tells me Shopify has 3,500 employees to Stripe's 9,500. Obviously neither company is compromised entirely of engineers, so this is a ballpark estimate.
GitHub feels like the real case where there might be a larger codebase. It's in the middle for employees (6,500), but it's existed longer than Stripe (though not as much longer as my gut feeling told me, interestingly)
I thought they used active_merchant
> currently amounting to over 15 million lines of code spread across 150,000 files
The monorepo has only gotten bigger over the last two years (source: I work at Stripe).
In general it was pretty rare, in my experience. The code bases were pretty well modularized.
Are they split into git-sub modules/ frameworks? Curious to know the development code review flow.
In our PR tooling, there's nothing that enforces/encourages scoping changes to a specific subset of any given repo. We generally encourage smaller PRs as a best practice, but a huge chunk of the benefit of a moonorepo is folks can make cross-cutting changes if/when necessary.
We have some custom goo on top of Github that manages the review flow. Specifically, we try to make it easy for folks to farm out reviews to the teams that own the code you're editing, so they don't have to hop in Slack and track down reviewers.