TribleSpace: Version-controlled knowledge graphs in Rust
ToolsComments
Tombstones were the death of several early distributed graph experiments in the 2010s, but modern compaction algorithms usually handle them without the performance cliff Mike is implying.
If they actually nail the S3 integration... the ability to share a massive knowledge graph as a simple pointer to a bucket would be a game changer for collaborative research...
S3 for an embedded knowledge graph? The latency for small, frequent reads on an embedded store would be a nightmare.
Regarding the S3 storage, is the project implementing a local caching layer or using a specific content-addressable chunking strategy to minimize round-trips?
We have tried Git-like versioning for local docs in my office; it is great until someone makes a massive change that breaks the merge logic for everyone else.
follows the trend of chronosdb moving state management into rust to bypass traditional server overhead.
The real delta isn't just the language, but whether they have solved the tombstone proliferation problem common in CRDT-based stores.
If TribleSpace uses an LSM-tree similar to Axion, the retrieval latency might actually be competitive for read-heavy workloads despite the CRDT overhead.