CRDTs merge concurrent edits. Why not concurrent creation?
Summary
Explores extending Conflict-Free Replicated Data Types (CRDTs) to handle concurrent creation, beyond their traditional ability to merge concurrent edits.
Similar Articles
CONCORD: Asynchronous Sparse Aggregation for Device-Cloud RAG under Document Isolation
CONCORD is an asynchronous sparse aggregation framework for retrieval-augmented generation (RAG) under document isolation in device-cloud setups. It improves throughput and reduces communication by orders of magnitude by treating the cloud as an asynchronously arriving evidence source rather than a continuously synchronized co-generator.
My Favorite Bugs: Invalid Surrogate Pairs
A blog post recounting a bug where inserting adjacent multi-byte emoji caused a splice in a CRDT library, splitting a surrogate pair and silently breaking collaborative editor synchronization.
A type-safe, realtime collaborative Graph Database in a CRDT
Codemix open-sources @codemix/graph, a type-safe, CRDT-backed graph database with TypeScript-native schema validation and realtime offline-first sync via Yjs.
@msimoni: One thing I keep thinking about: with S3-like object storage as primitive, you could build a transactional database wit…
A tweet discusses the idea of building a transactional database with infinite throughput using S3-like object storage and content-addressing, where blocks are written in parallel and the root hash is updated periodically.
How we solved concurrent write collisions and data loss in local-first multi-agent systems (LAC-Protocol)
Describes the LAC-Protocol for handling concurrent write collisions in local-first multi-agent systems, using lock-state separation and avoidance caching to prevent data loss and token waste.