<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>davidrupp</author><text>Datomic is bundled with a REST server: &lt;a href=&quot;http://docs.datomic.com/rest.html&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;docs.datomic.com&amp;#x2F;rest.html&lt;/a&gt;. And it includes an endpoint to subscribe to a stream of Server-Sent Events, which lets you drink from the transaction-report firehose. But there is a lot of data in that stream. I&amp;#x27;m writing a production Pedestal app, and I could definitely use the capability to store my data on the client in the same shape as Datomic and query it with Datalog.</text><parent_chain><item><author>drcode</author><text>Looks like a great library... It would be intriguing to try to use something like DatomicScript for the app state of an Om application.&lt;p&gt;(Edit: Read in a separate blog post that the author of DatomicScript is thinking about this already)&lt;p&gt;At the end of the day though, I still think someone (smarter than me) needs to figure out the full end-to-end solution for datomic+clojurescript, with both client and server elements.&lt;p&gt;The core question: Does it make sense to map datomic to a REST API on the server, then consume the REST on the client? Or, does it make more sense to build something more clojure-like for the client-server interface, and remove REST from the equation entirely?</text></item></parent_chain></comment><story><title>DataScript – Datomic in ClojureScript</title><url>https://github.com/tonsky/datomicscript</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dustingetz</author><text>i think you want the application-facing interface to remain REST (links between entities, HATEOAS), but the REST&amp;#x2F;CRUD client&amp;#x27;s transport layer wouldn&amp;#x27;t be traditional http&amp;#x2F;ajax, rather implement similar capabilities to a Datomic Peer. So a CRUD READ would query a cached Datomic index rather than touch network. Create, Update, Delete could be http&amp;#x2F;ajax or could be something else like a websocket; I believe transport to be orthogonal to the fundamental principles of REST application design.</text><parent_chain><item><author>drcode</author><text>Looks like a great library... It would be intriguing to try to use something like DatomicScript for the app state of an Om application.&lt;p&gt;(Edit: Read in a separate blog post that the author of DatomicScript is thinking about this already)&lt;p&gt;At the end of the day though, I still think someone (smarter than me) needs to figure out the full end-to-end solution for datomic+clojurescript, with both client and server elements.&lt;p&gt;The core question: Does it make sense to map datomic to a REST API on the server, then consume the REST on the client? Or, does it make more sense to build something more clojure-like for the client-server interface, and remove REST from the equation entirely?</text></item></parent_chain></comment><story><title>DataScript – Datomic in ClojureScript</title><url>https://github.com/tonsky/datomicscript</url></story>