Paxos lecture (Raft user study)
Channel:Diego Ongaro · Length:1:06:33 · Published:2013-08-15 · Views:114275
Summary
John Ousterhout's slides-and-voiceover lecture on Paxos, made for the Raft user study comparing how students learn Raft and Paxos. It is a full introduction to the Paxos consensus algorithm.
Why HN recommends it
Recommended as a clear, lucid way to learn Paxos and Multi-Paxos, ideally alongside the companion Raft video.
The 2 videos do an excellent job of explaining both the Paxos and Raft algorithms and the key differences between them. — HN, 2014
Distributed systems · University lectures & courses
Subtitles (excerpt)
hello I'm John osterhout and in this video I'm going to introduce the paxos consensus protocol paxos was invented by lesli Lamport in the late 1980s and since then it has become almost synonymous with the idea of consensus when universities teach consensus in classes they virtually always use paxos as the algorithm and most practical implementations of consensus are based in some way on paxos paxos has become perhaps the single most important algorithm in all of distributed systems I'm going to explain paxos in the context of creating a replicated log and then we'll use the replicated log to create a replicated State machine when I say State machine I just mean a program or application that takes inputs and produces outputs and holds some internal state so you can think of almost any program or application as a state machine the idea is that we'd like to make a state machine highly reliable and the way we'd like to do that is by having the same state machine run concurrently on several different servers and if each of those State machines receives the same set of commands in the same order then they should all behave identically and produce the same results so ideally if some of the machines crash
On Hacker News
I recently took a Distributed Systems course, and I also thought it was very interesting and unexpected how in the most basic form of Paxos, there is no concept of node roles or hierarchy like leader/follower, master/replica, etc. The base case is that all nodes have the same replicated log, and are "writers" capable of initiating changes to the log. This youtube video was particularly helpful in… — cljacoby, 2024-02
One of the most lucid explanations of the Raft Consensus Algorithm that I've ever seen is the one in John Ousterhout and Diego Ongaro's Raft User Study[0]. The 2 videos do an excellent job of explaining both the Paxos and Raft algorithms and the key differences between them. John's narration is extremely clear and the slides are very informative. Definitely recommended! Raft is a consensus algori… — krat0sprakhar, 2014-10
Raft is very similar to Multi-Paxos. These Raft and Paxos user studies comparing the "understandability" of the two protocols might be helpful: [VIDEO] (Paxos), [LINK] (Raft). See also, comparison of various "Paxos" implementations: [LINK] — ignoramous, 2021-07
IMO if you develop a good understanding of Paxos then learn TLA+ you'll know everything you need to work on production distributed systems. Learn about CRDTs too, just to see what eventually-consistent systems look like. The real core of distributed systems is less knowing specific algorithms and more knowing what makes the field so hard, what solutions are possible, and the limitations of those … — ahelwer, 2020-04
The first is a proof published in a paper that you can read. I recall the proof is for single decree paxos. In reality, you need multiple rounds. There are many subtle variations and I am not aware of a proof for that. Is an implementation correct? Frankly, that is a PhD thesis that is still to have been written. If you want to do a PhD and this topic burns inside you, go for it. Regarding consen… — brutus1213, 2017-03
Related videos
- Raft lecture (Raft user study) · Diego Ongaro · 58:17
- Slavoj Žižek on "They Live" (The Pervert's Guide to Ideology) · Christian G · 6:00
- Quantum Computing for Computer Scientists · Microsoft Research · 1:28:22
- AWS re:Invent 2016: Tuesday Night Live with James Hamilton · Amazon Web Services · 1:33:27
- Tracy Young Speaks at Female Founders Conference 2015 · Y Combinator · 26:51
- AWS re:Invent 2018: How AWS Minimizes the Blast Radius of Failures (ARC338) · Amazon Web Services · 55:43
- Zebras All the Way Down - Bryan Cantrill, Uptime 2017 · Code & Supply · 46:36
- Jeff Bezos 1997 Interview · Chuck Severance · 5:39
- Simulating an epidemic · 3Blue1Brown · 23:12
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- Advanced Topics in Programming Languages: A Lock-Free Hash Table · GoogleTalksArchive · 58:35
- DNA animation (2002-2014) by Drew Berry and Etsuko Uno wehi.tv #ScienceArt · WEHImovies · 7:19
- Hey Underscore, You're Doing It Wrong! · InfoQ · 36:30
- Keynote - JSON Graph: Reactive REST at Netflix · Association for Computing Machinery (ACM) · 54:57
- AWS re:Invent 2015 | (NET403) Another Day, Another Billion Packets · Amazon Web Services · 42:25
- A Philosophy of Software Design | John Ousterhout | Talks at Google · Talks at Google · 1:01:40
- Replace Your Exploit-Ridden Firmware with Linux - Ronald Minnich, Google · The Linux Foundation · 38:02