Content-Addressed Storage
ELI5 — The Vibe Check
Content-addressed storage stores data by its hash, not its name — deduplication and integrity verification baked directly into the model. The file's name is its fingerprint. The same content always gets the same address. If something gets corrupted, the address changes and you know immediately. Git does this for every commit, every file. Docker does it for image layers. IPFS does it for the entire web. Once you understand it, you start seeing it everywhere.
Real Talk
In content-addressed storage (CAS), the storage address of an object is derived by hashing its content (typically SHA-256). This provides three properties automatically: deduplication (identical content always maps to the same address, stored once), integrity verification (any modification changes the hash, making corruption detectable), and immutability (addresses never change once assigned). Git's object store, Docker's layer cache, and IPFS all implement CAS. It's the foundation of reliable distributed storage.
When You'll Hear This
"Our artifact store uses content-addressed storage — identical builds share the same cache." / "Git's integrity guarantees come from content-addressed storage. The hash IS the ID."
Related Terms
Abstraction
Abstraction is hiding the messy details and showing only what matters.
Docker
Docker is like a lunchbox for your app.
Git
Git is like a magical save system for your code. Every time you save (commit), it remembers exactly what changed.