Hey, yes you can use the REST api to talk to it from anything that can support an HTTP client: https://opencrux.com/docs#restapi

If you see the thread above i was trying to do exactly that 😄

Hey @UJMU98QDC building out interop and support for other languages + ecosystems is absolutely the intention. In the short-term we're already working on SQL and regular JSON APIs. Over the longer term we would like to offer GraphQL and native HTTP clients for various languages. What language/platform are you hoping to use currently?

1. NodeJS 2. Rust

Thinking loud here: could we bring code to crux, e.g. for in-db authorization or transaction processing? Using SCI or an embedded JS interpreter. :thinking_face:

@U054UD60U embedding a sandboxed interpreter is definitely interesting for tx processing, and we've discussed it a bit in the transaction function issue (which we only closed yesterday!): https://github.com/juxt/crux/issues/121#issuecomment-520563824 JS would probably be the better strategic choice if we do go down that route, but there are no firm plans on what to do with transaction functions next (asides from releasing them for the world to see 🙂) In-db authorization is already on our roadmap but I think we will strongly prefer to keep things declarative, so any kind of Turing-complete interpreter is unlikely.

Oh, interesting. I’m going to read the history of that issue.