@cjsauer for now we try to make datahike usable in the backend and will expand the synchronization from there. i agree that the biggest issue to address is to bridge the backend frontend gap in a consistent way. what form of distribution would you like to see addressed first?
To do so we need to replicate the hitchhiker-tree from the transactor to the clients. datahike does not yet work in cljs, because we have focused on making it useful on the JVM first. To make that work one needs to fix the hitchhiker-tree cljs support (it is there but currently not tested) and then extend async IO into the datahike codebase. That will be a bit annoying because async code is harder to debug. We have a way to compile it away for the JVM with the help of the macro system in the hitchhiker-tree, but probably should push that down the stack so that konserve also can work synchronously. At least datahike should use some optional async system like this: https://github.com/replikativ/hitchhiker-tree/blob/master/src/hitchhiker/tree/utils/async.cljc