corrosion

This looks cool! Curious, how does this compare to https://github.com/superfly/corrosion?

State replication is currently based on corrosion: https://github.com/superfly/corrosion

woof vlcn-io/cr-sqlite definitely built by someone who doesn't understand the fundamentals of the space > As of cr-sqlite 0.15, the CRDT for an existing row being update is this: (1) Biggest col_version wins col_version is definitely something, but it isn't a logical timestamp! -- https://github.com/superfly/corrosion/blob/main/doc/crdts.md > Crsqlite specifically uses a "lamport timestamp" which, if you squint at from a distance, could be most concisely boiled down to a monotonically increasing counter. lamport clocks can be boiled down to monotonically-increasing counters _per physical node in the system_, not per logical row/entity in the data model so if you want to do conflict resolution based on logical (lamport) clocks you need to evaluate/resolve concurrent modifications according to site-specific logical clocks and their historie

For the TL;DR folks: https://github.com/superfly/corrosion

Their client application (written in Go) is open source: https://github.com/superfly/flyctl They have a few other notable open source components, I think these two are particularly interesting: - https://github.com/superfly/corrosion - https://github.com/superfly/litefs (Disclosure: they sponsor some of my work.)

https://community.fly.io/t/reliability-its-not-great/11253 https://github.com/superfly/corrosion

Couchdb/pouchdb remains one of the best: it's super easy to setup and is production-ready, but it's gonna be json docs with no transactions, so it can be limiting. Y.js and automerge emerged as solutions combining CRDTs and content transfer, they look really promising. There is a Y.rs version if that's better for you. I've always dreamt of building something on top of Syncthing, ie something that would use file synchronization. It's more versatile and will definitely last longer than anything else, and it has some built-in capabilities for having a third party helping transport but not being allowed to read content. I recently came across https://github.com/superfly/corrosion , a service discovery and state management tool that is working completely p2p. CR-SQLite, in particular, allows multiple tables from multiple databases to be merged

Any thoughts here on Fly's Corrosion? https://github.com/superfly/corrosion

We’re using cr-sqlite as part of our distributed state propagation system. It is indeed easy to bundle in the app! https://github.com/superfly/corrosion It would be possible to distribute cr-sqlite changes in many different ways (like you said, http or torrents, etc.) since any change can be applied out of order.