3 ms·
"Consensus is a problem that has plagued computer science phd’s for literally decades" No, not really. The Paxos paper was in 1989. One might reasonably argu
by notacoward 12y ago
"Consensus is a problem that has plagued computer science phd’s for literally decades"
No, not really. The Paxos paper was in 1989. One might reasonably argue that Raft is an improvement, but if so it's only an incremental one - not a cure for a "plague" as the author suggests.
The same obliviousness to actual history and reality plagues (heh) the rest of the article as well. Saying that package managers were invented because "compiling code from source became cumbersome" is way off base. Tell it to Gentoo, which has long had a package manager to manage dependencies but still compiles locally. Also, the "ubiquitous overlay network that comes attached to all virtualized platforms" seems conspicuously non-ubiquitous except in the VMware universe.
I don't want to seem gratuitously negative, but the author's argument is incoherent. The conclusion that we need something like CoreOS might be correct, but counterfactual axioms do not support that (or any) conclusion. Containerization is not the solution to configuration-management problems. In fact, technologies such as Docker rely heavily on tools and lessons from the configuration-management space. Where they have abandoned that heritage, they have often left huge gaps (e.g. security). The evolution we're seeing has less to do with previous approaches not working than with combining and applying those approaches in new ways precisely because they have become robust/mature enough to do so.
- jfoutz 12y agoPart time parliament was written in 1989, but not published till 1998. Probably not fair to claim to much recognition of its value till the mid (late?) 90's. http://research.microsoft.com/en-us/um/people/lamport/pubs/pubs.html#lamport-paxos http://research.microsoft.com/en-us/um/people/lamport/pubs/p...
- notacoward 12y agoIt was published well before 1998, as SRC research report #49. http://apotheca.hpl.hp.com/ftp/gatekeeper/pub/dec/SRC/research-reports/abstracts/src-rr-049.html http://apotheca.hpl.hp.com/ftp/gatekeeper/pub/dec/SRC/resear... There were also other papers based on that before 1998, including the Petal/Frangipani stuff. That something already so well known wasn't "properly" published for nearly a decade was a bit strange, as Lamport himself explains in the page you cited. Even if that weren't the case, something that was published in 1998 still refutes the "plagued for decades" claim.
- jfoutz 12y agoInteresting. I'd thought that "The Paxos algorithm for consensus in a message-passing system was first described by Lamport in 1990 in a tech report that was widely considered to be a joke [1]" was pretty much the standard interpretation. Perhaps i'd read the Turing award writeup to literally. "Unfortunately the setting as a Greek parable made the paper difficult for most readers to comprehend, and it took nine years from submission to publication in 1998. But the 1989 DEC technical report did get noticed. Lamport's colleague Butler Lampson evangelized the idea to the distributed computing community [19]. Shortly after the publication of Paxos, Google's Chubby system and Apache's open-source ZooKeeper offered State Machine Replication as an external, widely-deployed service." It's a little odd, nobody seems to have actually used it before oh, say 2000 or so, but maybe it was in secret proprietary kinds of stuff. [1] http://www.cs.yale.edu/homes/aspnes/pinewiki/Paxos.html http://www.cs.yale.edu/homes/aspnes/pinewiki/Paxos.html [2] http://amturing.acm.org/award_winners/lamport_1205376.cfm http://amturing.acm.org/award_winners/lamport_1205376.cfm
- russell_h 12y agoPhDs may be only ones were both aware of consensus as a problem and not plagued by it. As a Zookeeper user however, I can promise you that anyone trying to actually implement or use consensus was very plagued.
- nl 12y ago> "Consensus is a problem that has plagued computer science phd’s for literally decades" No, not really. The Paxos paper was in 1989. One might reasonably argue that Raft is an improvement, but if so it's only an incremental one - not a cure for a "plague" as the author suggests. The problem with consensus for PhDs is not that Paxos doesn't solve it. The problem is that it is SO hard to understand. Notably, soon after Lamport's 1998 Paxos paper he published Paxos Made Simple[1] which noted The Paxos algorithm for implementing a fault-tolerant distributed system has been regarded as difficult to understand This paper was supposed to make it simpler, but it wasn't enough. When the Raft paper was release, the title was In Search of an Understandable Consensus Algorithm[2] which noted the following: most implementations of consensus are based on Paxos or influenced by it, and Paxos has become the primary vehicle used to teach students about consensus. Unfortunately, Paxos is quite difficult to understand,in spite of numerous attempts to make it more approachable. Furthermore, its architecture requires complex changes to support practical systems. As a result, both system builders and students struggle with Paxos I'd say that is reasonable evidence to suggest that, yes, consensus really has plagued computer science phd’s for decades. Additionally, I'd note that the famous maxim There are only two hard problems in computer science: Naming things and Cache Invalidation (and off-by-one errors) basically refers to the difficulties in establishing distributed consensus in both the "naming things" and "cache invalidation" cases. [1] http://research.microsoft.com/en-us/um/people/lamport/pubs/paxos-simple.pdf http://research.microsoft.com/en-us/um/people/lamport/pubs/p... [2] http://web.stanford.edu/~ouster/cgi-bin/papers/raft-atc14 http://web.stanford.edu/~ouster/cgi-bin/papers/raft-atc14