hesela.devVersion vector
A version vector maps actors to counters that summarize contiguous prefixes of update histories for a replicated object.
Componentwise comparison can identify equal, superseded or concurrent versions when the represented histories satisfy the protocol's assumptions. Missing components count as zero. [1]
An actor can denote a client or a replica; this choice affects correctness and metadata growth. A server counter must not silently imply that a client observed every earlier update registered by that server. [1]
Relations
Citations
Sources & caveats
- Source synthesis, not an executed replication protocol. No product lifecycle is implied by the unknown status.