Single Leader Replication - how it works | Systems Design 0 to 1 with Ex-Google SWE

preview_player
Показать описание
Single leader replication is my favorite type of replication since it removes me of myself (single leader, alpha male)
Рекомендации по теме
Комментарии
Автор

This entire system design playlist is awesome, so much is packed in these short videos, and your dry humour makes it even more fun to watch.👏

manishasingh-dehi
Автор

Bro you are awesome. Your sense of humor is too good, making learning system design fun

thanujakumar
Автор

Hey man I have been enjoying your system design concepts So far one suggestion I'd like to make is maybe you can talk along with your drawing (the 5 dollars white board you normally used in the end of each videos)
I think this can really help the explanation, anyway keep up with the great worj

yk
Автор

Hey Jordan, thanks a lot for this content! It's especially cool that you draw, because it makes so much more sense :)
Will you do the same "drawing" series with System Design Questions?

danilaosipov
Автор

Thanks a ton!! Waiting for more such awesome/harder ones

LeoLeo-nxgi
Автор

High Tech-Wizard 🌿🧑‍💻 Thanks for the hard work brotha

edzbnsb
Автор

Hi Jordan, can you please share the resources for the system design which you follow?

yaswanth
Автор

In regards to second problem you mentioned when the leader goes down, specifically the case where writes 71-80 are lost since those writes were never replicated.

I assume the new leader (previously the follower) begins accepting writes starting from write 71. When the initial leader that had gone down comes back online at a later point in time, the initial 71-80 records also come "back into existence".

My question here is, in such a case do we really lose the 71-80 data?

msebrahim-
Автор

Hello Jordan(Single Leader, alpha male), As always great video
I had a small query, as we have established replication can be achieved using Replication log. Just wanted to know how does this actually work between master and follower? Is it a process on master which keeps track of where exactly each follower is and pushes the difference OR each follower polls the master with last item it fetched and master sends back the new data it has.

sahilguleria
Автор

cant we just label a node as a leader / follower, or is this basically just what distributed consensus is?

huscooking
Автор

Hey Jordan, In a partitioned database that uses single leader replication, does each partition have it's own single leader or is there one leader across all partitions?

roadkill
Автор

In the leader goes down scenario 2 where we are loosing the data from 71-80. In this case don't we have a replication log for exactly that purpose. Like the leader wrote into the replication log till 80 and then dies. Since the follower is reading the replication log wouldn't it be able to get that data? Pls correct me if I am wrong!

eeoiqvf
Автор

Typo in video description?
It 'reminds' me of myself?

rajanwaliya