“Disk is the new tape.”
Jim Gray offered this line in his observations about changing storage hierarchies, later cited by Microsoft. Gray used the comparison to capture a shift caused by growing memory capacity and the widening latency gap between processors, memory, and disks. Disk remained valuable for large amounts of colder data, but random access increasingly looked too slow for the hottest workloads. Read in that setting, the quotation records a practical lesson earned through a particular technical challenge.
A familiar component can change roles even when it keeps improving. Sequential bandwidth and capacity may advance while latency makes the device unsuitable for work it once handled, pushing architects to reorganize data around a new hierarchy. The central issue is the relationship between capability, understanding, and responsibility. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The phrase is an architectural analogy, not a literal claim that disks became obsolete. Cost, durability, capacity, and workload shape the right tier. Technologies that look slow at one layer may remain essential at another. The limitation strengthens the argument because it identifies the conditions under which the idea can be applied responsibly. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
The same reasoning applies to object storage, memory, accelerators, and model caches. Teams should measure the access pattern they actually have and reconsider old boundaries when relative costs change, rather than treating yesterday’s hierarchy as a permanent law. That is a demanding standard, but it is more durable than judging progress by speed, scale, or attention alone. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Jim Gray offered this line in his observations about changing storage hierarchies, later cited by Microsoft. Gray used the comparison to capture a shift caused by growing memory capacity and the widening latency gap between processors, memory, and disks. Disk remained valuable for large amounts of colder data, but random access increasingly looked too slow for the hottest workloads. Read in that setting, the quotation records a practical lesson earned through a particular technical challenge.
The source record connects the wording to his observations about changing storage hierarchies, later cited by Microsoft, which is the context used for this post.
A familiar component can change roles even when it keeps improving. Sequential bandwidth and capacity may advance while latency makes the device unsuitable for work it once handled, pushing architects to reorganize data around a new hierarchy. The central issue is the relationship between capability, understanding, and responsibility. In practice, that means asking what changed, who gained new capability, which assumption carries the most risk, and how the result would be checked by someone who did not share the builder’s expectations. It also means comparing the claimed benefit with the maintenance, access, and recovery work required to keep it real over time. The quotation earns its place by sharpening those questions instead of closing them.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
The phrase is an architectural analogy, not a literal claim that disks became obsolete. Cost, durability, capacity, and workload shape the right tier. Technologies that look slow at one layer may remain essential at another. The limitation strengthens the argument because it identifies the conditions under which the idea can be applied responsibly. Strong technology reporting must preserve this boundary, because the same words can support very different choices after the original constraints disappear. Readers should be able to see both the useful principle and the evidence that would require a different judgment. A responsible reading separates the speaker’s documented claim from broader promises that admirers may attach to it later.
The same reasoning applies to object storage, memory, accelerators, and model caches. Teams should measure the access pattern they actually have and reconsider old boundaries when relative costs change, rather than treating yesterday’s hierarchy as a permanent law. That is a demanding standard, but it is more durable than judging progress by speed, scale, or attention alone. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. The same discipline should follow the system after launch, when real users reveal consequences no prototype fully predicted in advance. Those habits turn a memorable insight into work that readers, builders, and institutions can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.