Inside GitHub’s new Git storage architecture
Comments on “Inside GitHub’s new Git storage architecture”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
GitHub's engineering blog, written by Karthik Raman, describes "Rubicon," a Git storage design that keeps packs in Azure Blob Storage and puts only reference updates through a replicated compare-and-swap log, Ref-CAS. Compaction runs on separate nodes, and disposable virtual replicas serve requests. GitHub reports internal tests of 5,000 concurrent agents and 7,200 pushes per second on one repository, with low read latency. These figures are GitHub's own and unsourced. The design is in limited private preview, with broader rollout planned for early next year.
Why it ranked
No. 8 of 109 with a score of 0.70. The panel rated it highest on new information (0.92) and technical depth (0.88), lowest on substantiated (0.66). Placed No. 8, No. 12 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering write-up of a Git hosting storage architecture with concrete throughput and design specifics, though partly a product announcement with unverified benchmark claims and some promotional framing.
- AI judgeJudge 3gpt-5.6-luna
- A detailed primary engineering account of a new Git storage architecture, including coordination, consensus, caching, compaction, scaling requirements, and measured throughput. It is highly relevant to infrastructure and agent-driven development, with modest promotional framing and limited evidence details.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.70total under rubric v2.3
- Significance0.73
- Reader interest0.86
- Audience breadth0.72
- Practical relevance0.71
- Substantiated0.66
- Technical depth0.88
- New information0.92
- Counts against: Promotional0.21
- Counts against: Overclaim0.30
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.78 | 0.60 | 0.82 | 0.73 | 0.22 | +0.24 | +0.176 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.78 | 0.85 | 0.94 | 0.86 | 0.16 | +0.26 | +0.223 |
| Audience breadthHow many people who build technology does it concern? | 0.67 | 0.70 | 0.78 | 0.72 | 0.11 | +0.13 | +0.093 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.67 | 0.60 | 0.86 | 0.71 | 0.26 | +0.22 | +0.156 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.58 | 0.55 | 0.84 | 0.66 | 0.29 | +0.05 | +0.033 |
| Technical depthHow technically substantive is it? | 0.90 | 0.80 | 0.94 | 0.88 | 0.14 | +0.05 | +0.044 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.90 | 0.98 | 0.92 | 0.09 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.09 | 0.35 | 0.18 | 0.21 | 0.26 | −0.19 | −0.039 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.27 | 0.40 | 0.22 | 0.30 | 0.18 | −0.11 | −0.033 |
| Sum of contributions | +0.699 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.699 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-06/8/"><img src="https://rubric.hrih.si/badge/2026-11-06/8.svg" alt="Ranked #8 on Rubric, 6 Nov 2026" width="231" height="28"></a>Claim check
Claim check: 1 matches source · 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenBenchmark result
In internal testing GitHub demonstrated support for 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo while serving read traffic with consistently low latency.
The article gives no link or citation for it.
The article says “we’ve demonstrated the ability to support 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency”
The source says No source to compare with.
Matches sourceNumber
GitHub moved 99.99999% of repositories into Azure in the bridge phase of the migration.
The cited source says the same thing.
The article says “moving 99.99999% of repositories into Azure, scoping the write quorum to individual references”
The source says “99.99999% of the Git repositories on GitHub began living in two places at once: our own data centers and Azure”
Source cited by the article: github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure
No source givenNumber
The busiest repositories on GitHub.com currently receive at most dozens of writes in a single second, typically in short bursts.
The article gives no link or citation for it.
The article says “the busiest repositories on GitHub.com receive at most dozens of writes in a single second, typically in short bursts”
The source says No source to compare with.
No source givenNumber
Daily requests to one repository on GitHub grew about 4x from March to May.
The article gives no link or citation for it.
The article says “daily requests to one repository on GitHub from March to May, when its traffic grew about 4x”
The source says No source to compare with.
No source givenNumber
GitHub's first Blob Storage approach, a single-blob write-ahead log for references, achieved write throughput in the mid-hundreds per second.
The article gives no link or citation for it.
The article says “In practice, this netted us write throughput in the mid-hundreds per second”
The source says No source to compare with.
No source givenNumber
Ref-CAS allows reference state alone to be transacted in the tens of thousands of operations per second.
The article gives no link or citation for it.
The article says “These approaches allow us to transact reference state alone in the tens of thousands of operations per second”
The source says No source to compare with.
No source givenDate
GitHub says Rubicon design work began in May 2026, shortly after the initial Azure migration.
The article gives no link or citation for it.
The article says “In May of 2026, hot on the heels of the initial Azure migration, we started working on a design that could meet those demands”
The source says No source to compare with.
No source givenDate
The new architecture is in limited private preview now, with a broader rollout planned for early next year.
The article gives no link or citation for it.
The article says “It’s available in a limited private preview now, with a broader rollout early next year”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 5 pts, not on front page
Recorded for context only, checked 6 Nov 2026, 05:47 UTC. It played no part in the ranking.