Mergeable Containers: Solving Concurrent Child Creation Conflicts in CRDTs
By
czx111331
Front-window bakery material. Catches the eye, delivers the goods.
Summary
This article discusses a fundamental problem in JSON-like CRDTs (Conflict-free Replicated Data Types) where concurrent creation of child containers under the same Map key by different users leads to apparent data loss — only one container is visible in the current document state while the other exists only in history. The article presents Loro's solution called "Mergeable Containers," which derives container identity from the logical parent/key/type combination rather than the creation OpID, allowing concurrent creations to merge into a single shared child container instead of diverging.
Key quotes
· 3 pulledFrom the application's point of view, this looks like data loss.
This is a classic problem in JSON-like CRDTs.
Mergeable Containers let Loro peers concurrently create the same child container under a Map key and still merge into one shared child, by deriving identity from the logical parent/key/type instead of the creation OpID.
You might also wanna read
The transactional outbox pattern: keeping a database and Kafka consistent
How Frontend State Management Becomes a Distributed Monolith as Apps Scale
This article discusses how frontend state management in growing applications can evolve into a "distributed monolith" — where state becomes
medium.com·19d ago
Creating Pluggable Databases via ORDS REST APIs: Asynchronous Workflow with DBMS_SCHEDULER Jobs
This article demonstrates how to create or clone Pluggable Databases (PDBs) using ORDS (Oracle REST Data Services) Database REST APIs. It hi
thatjeffsmith.com·2d ago