Git at Any Scale
meetpateltech
30 points
3 comments
August 18, 2026
Related Discussions
Found 5 related stories in 161.2ms across 13,334 title embeddings via pgvector HNSW
- Scaling Git at OpenAI makeramen · 141 pts · November 02, 2026 · 71% similar
- Accelerating Development for Massive Git Repositories kumrayu · 11 pts · November 18, 2026 · 67% similar
- The bridge to agent-scale Git infrastructure Klaster_1 · 59 pts · October 21, 2026 · 66% similar
- git git git git git alexmolas · 41 pts · August 18, 2026 · 64% similar
- Lazygit amirmasoudabdol · 24 pts · September 05, 2026 · 63% similar
Discussion Highlights (3 comments)
ChrisArchitect
Related: Cursor Origin Code Hosting https://news.ycombinator.com/item?id=49334209
vegadw
Remember, don't put large objects in cnt, it makes it a real pain later.
biwills
> What about consensus? Elections? Which server is the primary for a given repository? It also doesn't matter! There's no state and no consensus here. Any server can be the primary. All updates to the write-ahead log are synchronized with an atomic compare-and-swap (CAS) operation on S3, so it's always safe for any instance of a repository to receive a push. Again reminded of what an amaizing piece of engineering S3 is (99.999999999% - 11 nines of durability) [1] 1: https://docs.aws.amazon.com/AmazonS3/latest/userguide/DataDu...