Isn't "consensus" just another word for "(eventual) consistency"? I don't see how you could build a distributed database without tackling the consensus problem.
More information can be found here: https://p2panda.org/specification/replication. The basic data sync is based on an append only log. But I can't find any information on what are the strategies for dealing with conflicts. If any of the contributors see this, could you comment on this please. Thanks!
Check out our section on "Operations", this is the data type we've built on top of the append-only log structure for multi-writer and conflict free data editing: https://p2panda.org/learn/operations
> Isn't "consensus" just another word for "(eventual) consistency"?
In my head, there's a distinction. Consensus can be used for non-commutative operations, whereas signed CRDT chains can operate entirely without any form of "agreement" other than how they are applied (see https://news.ycombinator.com/item?id=30560573). I wouldn't call distributed CRDTs "consensus."
