Thank you so much for creating the tudo example. I'm learning a lot from it.
I want to make sure I understand your implementation of CRDT. Please let me know if this correct:
To use CRDT for a generic table, the following fields are added:
is_deleted: used for soft deletes
node_id: contains the ID of the node creating/modifying the record.
hlc: the timestamp for record creation/modification appended with the ID of the mutating node
modified: the timestamp for the record entry/update on the current node (not changes to the data), appended with the node ID where the record is being saved
If this is correct, then I have two questions:
Isn't appending the node ID to the modified field redundant since the node writing the record would know its own ID?
Isn't appending the node ID to the hlc entry redundant, since that value will always be equal to the value of the node_id field? Or is it needed for compatibility with earlier versions of the code?
Thank you so much for creating the tudo example. I'm learning a lot from it.
I want to make sure I understand your implementation of CRDT. Please let me know if this correct:
To use CRDT for a generic table, the following fields are added:
If this is correct, then I have two questions: