seminal

Weekly Paper Notes — the Seminal Paper of the Week for the 2026-10-03 digest. Area: Networking / Systems. Authors: Van Jacobson (Lawrence Berkeley Laboratory), with Michael J. Karels (UC Berkeley) on the revised version Published: Proceedings of ACM SIGCOMM ‘88, Stanford, August 1988; Computer Communication Review 18(4), pp. 314–329. DOI: 10.1145/52324.52356 Why the paper still matters In October 1986 the link between Lawrence Berkeley Laboratory and UC Berkeley, about 400 yards apart and three gateway hops, went from 32 kbit/s to 40 bit/s....

Weekly Paper Notes — the Seminal Paper of the Week for the 2026-08-29 digest. Area: Operating Systems. Authors: Dennis M. Ritchie and Ken Thompson (Bell Laboratories) Published: Communications of the ACM, Vol. 17, No. 7, July 1974, pp. 365–375. DOI: 10.1145/361011.361061 Why the paper still matters Most influential systems papers describe something large. This one describes something conspicuously small, and the smallness is the argument. The system it presents ran on a PDP-11/45 with 144K bytes of core, of which the resident kernel occupied roughly 42K — about 16K words of code and data....

Weekly Paper Notes — the Seminal Paper of the Week. Area: Distributed Computing. Authors: Douglas B. Terry, Marvin M. Theimer, Karin Petersen, Alan J. Demers, Mike J. Spreitzer, Carl H. Hauser — Xerox Palo Alto Research Center Published: SOSP ‘95 — Proceedings of the 15th ACM Symposium on Operating Systems Principles, pp. 172–182 DOI: 10.1145/224056.224070 Why the paper still matters There is a version of distributed systems history in which “eventual consistency” arrives with Dynamo in 2007, gets popularised by the NoSQL wave, and is eventually formalised by CRDTs....

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....