Clojurians Log v2

At the moment Datahike runs in your application process with one backend per connection. But you can have multiple connections to the same backend.

@konrad.kuehne can the multiple connections come from different Java processes entirely?

No, because datahike wouldn’t know if something has changed on disk. You would need to add file-listeners in order to do that and reconnect once something has changed. Last year I used the dat protocol in order to sync databases. You would need to do something similar as in https://github.com/kordano/datahike-sync/blob/master/src/datahike_sync/core.clj#L72.

@zhuxun2 Datahike is definitely designed to work with multiple concurrent clients, we just have not implemented distributed connection management yet. We are currently working on https://github.com/replikativ/datahike-server/ which can provide an interface to concurrent requests in many different languages. It just does not run the query on the client side yet (as Datomic does).

@konrad.kuehne wrote about the replication he linked above here: https://lambdaforge.io/2019/12/08/replicate-datahike-wherever-you-go.html