Clojurians Log v2

> I can not use await-tx with a tx on another node, right? Actually you can 🙂 the submit-tx receipts can be passed around freely between clients of completely different nodes. The only caveat is that each node may be at a completely different place in the log, so the time spent awaiting may vary substantially depending on which node the request is made to. I haven't got a terribly strong grasp of linearizability and all the theoretical definitions that implies, but I believe the extreme version is avoiding stale reads across all clients, and this would require there to be a kind of global "read lock" (managed by something like Zookeeper) that ensures all nodes coordinate to make each new basis-t available across all clients atomically.

the sync api (which Crux also provides) is essentially the same as communicating the submit-tx receipts between all the nodes and then using await-tx, but that still doesn't address this notion of reads being stale by the time the subsequent query has returned I vaguely recall having a conversation with someone about another possible solution, which is to run linearizable queries inside a transaction function and publish the results via side-effects. I may be crossing wires at this point though 😅

thanks so far. I want to understand Crux some more, so I will have to take a deeper look. :thumbsup: