Why separate Git objects from references?
Git objects are content-addressed and immutable, while references such as branches move as commits are added. Treating those write patterns separately can reduce coordination around large pushes, but the implementation still must preserve consistent ref updates.
Answered in
GitHub’s New Git Storage Design Separates Objects From RefsGitHub’s storage redesign separates immutable Git objects from mutable references, targeting high push concurrency while preserving Git semantics.
Read the full analysisOther questions this article answers
More development best practices questions
- Does GitHub’s new storage architecture change Git commands?
- Is the new architecture generally available?
- Does the new overview page change pull request merge requirements?
- What does GitHub’s pull request overview show?
- Is the overview page enabled by default?
- What streaming protocols does Google Cloud API Gateway support in preview?
- Can an existing API Gateway API be changed to streaming later?
- What is the main operational risk when proxying streamed responses?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.