talk-raft-consensus

https://m.youtube.com/watch?v=LAqyTyNUYSY

Replicated state machine

At seven minutes talks about multi-region database

At 9:05 the authors of the paper-chubby-lock-service talking about how PAXOS is usually not implemented correctly.

At 9:20 They designed raft with understandability-as-a-design-goal.

At 9:45 using is innocent to explain as a design criteria. TODO, get actual quote

At 12:30 leader election, log replication, and safety

At 14 minutes leader election visualization

At 37 new leader defers committing entries from prior term. He says something about reading paper-raft to learn more about that.

talk-raft-consensus#hydrabase-multi-region-database At 44 hydrabase, which is a Facebook use of raft for multi region database says talk-raft-consensus#hydrabase-multi-region-database

talk-raft-consensus#log-compaction-and-snapshotting At 47:20 he talks about log compaction and snapshot it, mentions that he goes into much more detail in paper-raft talk-raft-consensus#log-compaction-and-snapshotting

At 49 he talks about the term number, and how a logical lock is necessary for any of these systems.

talk-raft-consensus#pushing-for-understandability-alters-your-choices At 51:50 he talks more about how pushing for understandability alters choices made. For example raft has four message types where a competitive algorithm has 10. Additionally every part of the algorithm must be motivated by something. There is less extraneous stuff. talk-raft-consensus#pushing-for-understandability-alters-your-choices

Referring Pages

understandability-as-a-design-goal