Arc — Yandex’s internal VCS for a monorepo
summary
Yandex built an internal version-control system called Arc to manage its huge monorepo. The talk explains problems with standard VCS tools at that scale, surveys systems they tried, and describes Arc’s design and techniques used to make working with the monorepo practical.
AI-written summary · about
chapters (19)
- 0:00Introduction to Arc
- 1:15Yandex monorepo scale
- 3:33Version control history
- 4:59Why SN was chosen
- 6:23Reasons to switch to Arc
- 7:26Dual VCS problems
- 9:13Arc architecture overview
- 11:02Virtual file system
- 13:08FUSE performance issues
- 15:14Arc daemon internals
- 17:24Lazy checkout
- 21:40Commit history at scale
- 24:28Five years of Arc
- 25:08Arc synchronization
- 26:55Shards and native FS
- 27:39Git repository conversion
- 29:21Developer simplified flow
- 31:51Arc open sourcing?
- 45:17Q&A
related talks
19m"Embracing Monorepo and LLM Evolution"
21mGit submodules: we have monorepo at home
05mHigh Speed Monorepos with high quality DX
36mYour Repository Knows More About Your Team Than Your Team Does
23mMonorepos & Spaceships - Navigating successfully through Code and Cosmos
29mMonorepos, are they right for you?
19mKeynote: Why Monorepos
29mVirtual Mono-Repo & Bazel