flâneur

Git's database internals V: scalability - The GitHub Blog

github.blog · 3,710 words · saved by 1 readers

Learn about artificial intelligence and machine learning across the GitHub ecosystem and the wider industry. Learn how to build with generative AI. Change how you work with GitHub Copilot. Everything developers need to know about LLMs. Machine learning tips, tricks, and best practices. Explore the capabilities and benefits of AI code generation and how it can improve your developer experience. Resources for developers to grow in their skills and careers. Insights and best practices for building apps. Tips & tricks to grow as a professional developer. Improve how you use GitHub at work. Learn how to move into your first professional role. Stay current on what’s new (or new again). Learn how to start building, shipping, and maintaining software with GitHub. Get an inside look at how we’re building the home for all developers. Discover how we deliver a performant and highly available experience across the GitHub platform. Explore best practices for building software at scale with a majori

Git's database internals V: scalability - The GitHub Blog Derrick Stolee · @derrickstolee September 2, 2022 | 17 minutes Share: This week, we are exploring Git’s internals with the following concept in mind: Git is the distributed database at the core of your engineering system. When the database at the core of an application approaches scale limits of a single database node, a common strategy is to shard the database. By splitting the database into multiple components, we can scale beyond the limits of a single node. For Git, large repositories can have a similar feeling. While the

related reading