HN Hall of Fame Weekly email

Why Google Stores Billions of Lines of Code in a Single Repository (2016)

cacm.acm.org Essays & writing Essays & articles Software engineering Candidate

Resurfaced independently across 3 calendar years, with breakout response in 2 of them.

submissions
6
submitters
6
observed span
2018–2022
peak thread · 281 comments
478 pts
latest 20+ return · 2020-01-11
112 pts

Submission timeline

2007–2026

One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.

First comments on top threads

HN comment order

I feel terrible for anyone who sees this and thinks, “ah! I should move to a monorepo!” I’ve seen it several times, and the thing they all seem to overlook is that Google has THOUSANDS of hours of effort put into the tooling for their monorepo. Slapping lots of projects into a single git repo without investing in tooling will not be a pleasant experience.

hobls·478-point thread·

Seems like this gets re-posted every few months. We don't actually have a single repository, although Google3/Piper really is huge and dominant. Android, Chrome, Fuchsia, and myriads of other projects don't exist in the monorepo (well, they are mirrored there) because the tooling and libraries there are really geared towards server deployment, not devices.

The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.

Breakout years
2

100+ points or 50+ comments

Total points
607

reference only — not used in Hall rules or ranking

Total comments
403

reference only — not used in Hall rules or ranking

Every submission