@@CraneMoon I am having problem with some of the code, I downloaded the code from their code, and I am trying to figure out what each part is, will you be able to help me out, please ?
Each peer sends it's whole version vector with each message. So, when peer 2 sends the "Delete" operation, that message will have "SiteId: 1; Counter: 24" as well as "SiteId: 2; Counter: 6" in it's version vector. Look into "vector clocks" for more info. Martin Kleppmann has a nice video on his channel.
As he already said, insertion will apply first. So it's obvious that the latest OP (which is 24 (insert)) will update the Version Vector Record from OP23 to OP24. Then the deletion will apply. Hope i'm not wrong
Those who didn't get the version part : What he wanted to mean is, when the peer1 sends an insert operation then the version vector for peer1 in peer2 is updated to 24 but the version vector for peer1 in peer3 is still 23 so it doesn't accept the change from peer2 because the version vector of peer1 in peer2 does not match with the version vector of peer1 in peer3 so it waits for the updation from peer1.. when the version is uniform across all peers then it accepts the action... I hope I'm not wrong.. :)
Awesome presentation, thank you
This is just what I needed for my project. Thanks!
hi, do you understand the whole concept
@@daviesoyasor3567 I think I did? I don't recall lol
@@CraneMoon I am having problem with some of the code, I downloaded the code from their code, and I am trying to figure out what each part is, will you be able to help me out, please ?
@@daviesoyasor3567 can you please share the link to the code.
didnt understand the version part. you have 23 for site 1 on record, how do u know Site 1 has gone to op 24 ?
same here. Are they increasing independently?
same here. Unclear on the version vector part explanation.
Each peer sends it's whole version vector with each message.
So, when peer 2 sends the "Delete" operation, that message will have "SiteId: 1; Counter: 24" as well as "SiteId: 2; Counter: 6" in it's version vector.
Look into "vector clocks" for more info. Martin Kleppmann has a nice video on his channel.
As he already said, insertion will apply first. So it's obvious that the latest OP (which is 24 (insert)) will update the Version Vector Record from OP23 to OP24. Then the deletion will apply. Hope i'm not wrong
Those who didn't get the version part :
What he wanted to mean is, when the peer1 sends an insert operation then the version vector for peer1 in peer2 is updated to 24 but the version vector for peer1 in peer3 is still 23 so it doesn't accept the change from peer2 because the version vector of peer1 in peer2 does not match with the version vector of peer1 in peer3 so it waits for the updation from peer1.. when the version is uniform across all peers then it accepts the action...
I hope I'm not wrong.. :)
16:40 anyone understood what he said?
Its so weird to be recommended a video on youtube, flick to 6 minutes in and see yourself quoted.
Haha. Could it be that your friends in youtube algorithm team are behind this?
gr8