Git's database internals I: packed object store - The GitHub Blog
This blog series will examine Git’s internals to help make your engineering system more efficient. Part I discusses how Git stores its data in packfiles using custom compression techniques.
Git's database internals I: packed object store - The GitHub Blog Derrick Stolee · @derrickstolee August 29, 2022 | 22 minutes Share: Developers collaborate using Git. It is the medium that allows us to share code, work independently on our own machines, and then finally combine our efforts into a common understanding. For many, this is done by following some well-worn steps and sticking to that pattern. This works in the vast majority of use cases, but what happens when we need to do something new with Git? Knowing more about Git’s internals helps when exploring those new solutions
related reading
- Git's database internals V: scalability - The GitHub Bloggithub.blog
- Git at any scalecursor.com
- Using Gitcs61bl.org
- Build Your Own Databasenan.fyi
- Git from the Bottom Upjwiegley.github.io
- How to Write a Git Commit Messagecbea.ms
- Get up to speed with partial clone and shallow clone - The GitHub Bloggithub.blog
- Code Storage by the Pierre Computer Companycode.storage
- Useful git commands for SRE and DevOps engineersreliabilityengineering.substack.com
- How Core Git Developers Configure Git | Butler's Logblog.gitbutler.com
- A successful Git branching model >> nvie.comnvie.com
- Why GitHub Actually Won | Butler's Logblog.gitbutler.com