https://docs.datomic.com/on-prem/rest.html

my answer isn't going to be particularly useful to you, but i've been picking apart this working nodejs + datomic cloud library in order to hopefully make a working cljs native version (and also explore a python client). https://github.com/csm/datomic-client-js

so far it has been... tedious

That's amazing, i could translate your project to ruby as I only need a tiny subset. Reverse engineering the api seems like such a interesting approach

definitely! that project isn't mine though; i'm just reverse engineering it to port it to cljs and maybe python (like you might for ruby).

it's a very useful blueprint and reveals some of the communication layers of Datomic Cloud. a big thumbs up to the author.

It feels like such a step backwards compared to the REST doc though. There was so much potential there (evident by the many languages who have support for it)

i have to agree with you there. Datomic Cloud was a huge step to making Datomic accessible without the sysadmin overhead, and Ions did the same for deploying Clojure code without the devops. that being said, AWS promotes Lambda as a cloud-wide connective tissue (as does Ions i guess), and i have a laundry list of use cases for language support outside the JVM

i asked the same question you did a few months ago and someone recommended rolling out my own Ion to proxy queries over an endpoint. it sounds like a fun project but there are probably things to consider, like how to secure it

... meanwhile over in Neo4j land 😉 https://neo4j.com/docs/http-api/current/

@U0GC1C09L this lib does exactly what you want but not yet for cloud https://github.com/vvvvalvalval/datomock/issues/6

thanks for sharing. i'm sticking to dev-local as being the "official" solution at the moment, and starting from a cloud db (whether remote or imported locally) is a must. no on-prem for me 🙂