An educational side project in Elixir, Phoenix, and Tauri. I share what I learned while wiring Automerge into the BEAM, including how I surfaced edit and delete conflicts for users.
What I’m very interested in is khepri implementation for an automerge storage. I doubt it’s possible without a very tight integration via a NIF or a C node running the Automerge side and calling back to BEAM for persistence.
Thanks for the note. Will keep it in mind.
I don’t know anything about automerge (so thanks for your post, I lrarned some new stuff), but it sounds very familiar.
LotusNotes (whether you like the app or not) kind of used a similar replication approach, and the replication is awesome.
CouchDB has that same approach and is a really tested solution. Also it’s written in Erlang (the server at least, but clients exist in many languages). Thus, if you haven’t done so’ you might want to look at it






















