content addressing
Storing and finding data by a hash of its content instead of by a name someone chose.
In more detail
The address of each piece of data is its hash, so identical content always gets the same address and is stored only once. Any change to the content gives it a new address, and a copy can be verified simply by hashing it again.
Examples
A registry can store artifacts by content address, so the digest a pipeline records always fetches exactly the bytes it tested.Git names every file, directory listing and commit by the hash of its content.Related terms
- digest — A SHA-256 hash of an image's manifest that identifies its exact content and can never be moved to other bytes.
- registry — A server that stores images and lets clients push and pull them by name, tag or digest.
- hash — A short fixed-length fingerprint calculated from data, which changes completely if even one byte of the data changes.
- layer — One read-only slice of an image that records the files a single build step added, changed or deleted.
- cache — A store of earlier answers kept close to where they are needed so they can be reused instead of fetched or computed again.
- remote caching — Storing build outputs on a shared server so that any developer or CI machine with the same inputs can download the result instead of rebuilding.
- object ID — The hash that names a Git object, such as a commit, and that you type to refer to it.
- Git object — One item in Git's database, a blob, tree, commit or annotated tag, stored under the hash of its content.
Taught in
- Building And Versioning The Artifact — DevOps & Site Reliability Engineering
- Pull And Inspect A Third Party Image — Docker Architecture & Production Containers
- Build, Test And Promote The Same Image In CI — Docker Architecture & Production Containers
- Unified Build Pipelines: Caching & Dependency Graphs — Production Full-Stack Engineering
- What A Commit Really Is — Advanced Git Internals & Distributed Workflows