seminal

Weekly Paper Notes — Seminal Paper of the Week. Area: Databases. Author: E. F. Codd (IBM Research Laboratory, San Jose) Published: Communications of the ACM, Vol. 13, No. 6, June 1970, pp. 377–387 DOI: 10.1145/362384.362685 Why the paper still matters Codd’s paper is eight pages long, contains no system, no benchmark, and no evaluation section. It would very likely struggle to get past a modern program committee. It is also, by a wide margin, the most economically consequential paper in the history of computer science — the entire relational database industry, SQL, the query optimizer as a discipline, and by extension most of what we call “data infrastructure” descend from it....

Weekly Paper Notes — the Seminal Paper of the Week for the 2026-08-08 CS paper digest. Area: Programming Languages / Concurrency (rotating away from a long run of distributed-systems picks). Author: C. A. R. Hoare (Queen’s University, Belfast) Published: Communications of the ACM, Vol. 21, No. 8, August 1978, pp. 666–677 DOI: 10.1145/359576.359585 Why the paper still matters If you have written ch <- v in Go, spawned an Erlang process and sent it a message, wired up an actor in Akka, or reasoned about a Rust mpsc channel, you have been programming in a dialect of a language sketched in eleven pages of CACM in 1978....

Weekly Paper Notes — 🔁 Seminal Paper of the Week, 2026-08-01. Area: Operating Systems / Storage. Authors: Mendel Rosenblum, John K. Ousterhout (University of California, Berkeley) Published: ACM Transactions on Computer Systems, Vol. 10, No. 1, February 1992 (SOSP ‘91) DOI: 10.1145/146941.146943 Why this paper still matters Almost every high-performance storage system built in the last fifteen years is a log-structured file system wearing a different name. LevelDB, RocksDB, Cassandra, HBase, Kafka, every SSD’s flash translation layer, ZFS’s copy-on-write, btrfs, WiredTiger, Lucene’s segment merges — all of them convert random writes into sequential appends and then run a background process to reclaim space....

Weekly Paper Notes — 🔁 Seminal Paper of the Week for the 2026-07-25 CS paper digest. Area: Distributed Computing. Authors: Leslie Lamport, Robert Shostak, Marshall Pease (SRI International) Venue: ACM Transactions on Programming Languages and Systems, Vol. 4, No. 3, July 1982, pp. 382–401. DOI: 10.1145/357172.357176 · PDF (SRI copy) Why the paper still matters Almost every distributed system in production today — Spanner, etcd, ZooKeeper, Kafka, every blockchain, every consensus protocol with a Greek letter in its name — is a descendant of the impossibility and possibility results in this 20-page paper....

Original: Leslie Lamport, Paxos Made Simple, ACM SIGACT News 32(4), December 2001. Canonical PDF: lamport.azurewebsites.net/pubs/paxos-simple.pdf Predecessor: The Part-Time Parliament, ACM TOCS 16(2), 1998 (the “island of Paxos” allegory that nobody could read). Why “made simple” Lamport originally described his consensus algorithm in 1998 in The Part-Time Parliament, a paper framed as archaeological reconstruction of the parliamentary procedures of an ancient Greek island. It was a joke. It was also, by broad consensus (pun deliberate), unreadable — reviewers hated it, adoption was near zero for years, and even engineers who wanted to build on it complained they couldn’t....

Weekly Paper Notes — Seminal Paper of the Week for the 2026-07-11 CS paper digest. Area: Distributed Computing / Coordination. Author: Mike Burrows (Google) Venue: OSDI ‘06 — The Chubby lock service for loosely-coupled distributed systems Canonical link: OSDI ‘06 proceedings · PDF Why the paper still matters Twenty years after publication, Chubby is the paper you can point at to explain almost every coordination system in the modern datacenter....

Paper: Spanner: Google’s Globally-Distributed Database, Corbett et al., OSDI 2012. Canonical URL: research.google/pubs/pub39966 Every week we spotlight a foundational paper that still shapes how systems are built. This week — as the digest surfaces new BFT consensus (Cadence) and NVM storage (FlintKV) work — we rotate to databases and revisit the paper that arguably did the most to reset the industry’s assumptions about what a distributed OLTP system can offer: Spanner....

Weekly Paper Notes — Seminal Paper of the Week for the 2026-06-27 CS paper digest. Area: Distributed Computing. Author: Satoshi Nakamoto Published: October 31, 2008 (cryptography mailing list) Canonical URL: bitcoin.org/bitcoin.pdf This week’s digest had a fresh paper on transaction-fair ordering on DAGs without weak edges (Tilikum, 2606.27250) — a piece of work whose entire problem statement (DeFi, BEV, reordering attacks) only exists because of one nine-page document published seventeen-and-a-half years ago to a small cryptography mailing list....

Seminal Paper of the Week — the paper that quietly defined what “cloud storage” looks like from the inside. Authors: Sanjay Ghemawat, Howard Gobioff, Shun-Tak Leung (Google) Published: SOSP ‘03 — 19th ACM Symposium on Operating Systems Principles, October 2003. Canonical link: The Google File System (Google research mirror) · ACM DOI 10.1145/945445.945450 TL;DR In 2003, Ghemawat, Gobioff and Leung described how Google was running a multi-thousand-node, petabyte-scale distributed file system on commodity hardware — and how the design assumptions diverged so sharply from the established POSIX-file-system lineage that almost every architectural decision in the paper looks like a heresy until you read the workload section....

Seminal Paper of the Week — a foundational systems paper that quietly shapes how every distributed system you use is layered. Authors: Jerome H. Saltzer, David P. Reed, David D. Clark (MIT) Published: ACM Transactions on Computer Systems 2(4), November 1984. Canonical link: End-to-End Arguments in System Design (MIT) · ACM DOI 10.1145/357401.357402 TL;DR The end-to-end argument is a layering principle: a function should be implemented in a lower layer of a system only when it can be completely and correctly implemented at that layer, and when implementing it there provides a clear performance benefit over implementing it at the endpoints....