I was reading your book and got tired at the beginning of chapter 8 then I found your YouTube channel while trying to watch some videos before I dig into the chapter! Thanks for all your work in making this field more understandable.
As soon as I find enough time I'm going to go through all the series. Thank you for making the effort.
Thanks for putting these lectures on youtube--education should be accessible to all
Mr. Kleppmann , I love your book and the way you explain things in your videos. Thank you so much for creating this material.
"Consistency" [0:11] ACID Read-after-write-consistency (lecture 5) Replication Consistency model Distributed transactions [2:26] Atomic commit versus consensus [4:47] >1 propose | all votes any 1 proposed value decided | must all commit/abort crash tolerated | abort if 1 node crash Two-phase commit (2PC) [6:33] (key moment) [9:45] The coordinator in two-phase commit [10:25] Fault-tolerant two-phase commit (1/2) [12:58] Fault-tolerant two-phase commit (2/2) [16:43]
Delighted to watch the series. Thanks for creating this. I am already grateful to you because of "DDIA"
Great lecture, straight to the point. Thanks for the effort put into it and the adequate way of explaining it.
Crystal clear explanation. Hats off to you, Martin!
Legend!! Im passing this course cuz of this playlist, the whole distributed systems in 1 day thanks to you <3
Great lectures, Great book, Great author 👍
Please correct me if i missed something..Before client sends commit message to coordinator for 2 phase commit start..it perform normal transaction on replicas but my confusion is if the problem happens during that write i.e. one replica performed write but another fails then how two phase will help...i thought that the entire reason of two-phase commit is to perform write in prepare phase and the commit in commit phase...why we are allowing normal update to both replicas before 2pc can start the process.
you my guy are a gem of humanity
Wow, I didn't know Martin has a YT channel. Instant subscribe.
Grateful for the amazing lecture! Finally, get some impression about how Raft works.
super illustrative. Thank you!
Hello, the video is so helpful but hope that my question can be clarified, best. Does the coordinator node care if other nodes have committed successfully or not, if it does and a node failed to commit, does the coordinator make a second decision for sending an abort to all the nodes?
Question: Why is the "prepare" message necessary if replicas "ack" on the original transaction message?
Am I right in understanding that we can use raft to send total order broadcasts and elect new coordinators for node communication and two phase commit for commiting data?
Why client is opening transaction simultaneously on 2 nodes in 2PC ? shouldn't the transaction be open on master node only ?
@Alvaro-hm9vu