Your understanding is right. Streaming datomic-esque facts to the client and storing them in datascript is a beautiful thing when it suits your problem. There might be some trade-offs wrt memory usage on the client and server, and the size of the payload to bootstrap the client-side database. But this is an architecture I would certainly choose when it fits.

Thank you for answering me. I'm trying to understand what you said. As examples for good fit use case for this structure, Dropbox or note taking apps are my first thoughts i could imagine. But if i want to build something like novel platform that depends on single database endpoint which has lots of clients looking into it. then it'll be not good fits. Because it simply can't sync the whole server and client data. Is that right? And in that case, is graphQL a good option? or is there some magical alternative option only exists in clojure world..? 😀

oh why yes, there is: https://pathom3.wsscode.com/docs/

+1

Thank you guys!