/tags/automerge/ Recent content in Automerge on Liangrun Da's website Hugo -- gohugo.io en Tue, 13 Jun 2023 00:00:01 +0200 /posts/automerge-internal-2/ Tue, 13 Jun 2023 00:00:01 +0200 /posts/automerge-internal-2/ Storage From operations to changes Before applying operations received from other actors, it’s necessary to ensure that they are causally ready. This rule applies to most Operation-based CRDTs 1. We can use vector clocks to ensure that all operations are causally applied, but it is not Byzantine fault tolerant. Another way is to use Hash DAG 2. By recording the dependencies of each operation, other actors can determine if it is causally ready when they receive it by checking if its dependencies exist in the current OpSet. /posts/automerge-internal-1/ Tue, 13 Jun 2023 00:00:00 +0200 /posts/automerge-internal-1/ Runtime Operation Set Operation Set (OpSet), as the name suggested, is a set of operations. It is the runtime data structure of Automerge, that enables the creation, retrieval, updating, and deletion of objects. The merging of two documents is conceptually the union of two operation sets. Everytime we update, delete or create an object, we insert an operation into the OpSet. And the retrieval of an object is actually the retrieval of an operation of the OpSet.