"Embracing Monorepo and LLM Evolution"
summary
Reimplements Git internal storage in Rust and builds a database-backed monorepo engine called Mega that stores decoded packfiles in a DB and reserializes Git packed objects on clone, complemented by a C tool to mirror Git structure for compatibility; cites Google Piper’s 186 TB, 35M commits scale as motivation; integrates Bazel backends for builds, wraps the engine in a Tauri app for local control, uses GTM zero-trust for peer relay and a decentralized LLM distro (Ming); prototype stage with a few projects already using Mega.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:56What is a monorepo
- 2:12Monorepo at Google Meta Microsoft
- 3:53Git limits for large repos
- 5:31Git internals storage issues
- 7:28Database-backed Git storage
- 8:20Mega monorepo engine
- 9:14CrisPro and Mega
- 10:06Build systems workflows
- 10:30Decentralized services GitHub limits
- 11:24Designing decentralized Git host
- 12:38Zero-trust model for networks
- 13:28Large files LLM distribution
- 14:33Mega user-friendly monorepo
- 16:34Decentralized code workflow
- 17:52Ming project LLM distribution
- 18:38Status and future roadmap
related talks
19mKeynote: Why Monorepos
29mModularity and Monorepositories
31mMonoRepos for the Masses
20mBuilding with Monorepos
41mHandling Monorepos Today
19mEscaping Chaos: Strategies to Move from Polyrepo to Monorepo
35mThe Gentle Monorepo - Ship Faster and Collaborate Better
46mExploring the power of monorepos: When and why to use them