This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-03
Channels
- # aleph (2)
- # announcements (6)
- # babashka (6)
- # beginners (106)
- # biff (8)
- # clara (24)
- # clj-kondo (10)
- # clj-otel (4)
- # cljdoc (2)
- # clojure (54)
- # clojure-conj (3)
- # clojure-europe (85)
- # clojure-norway (54)
- # clojure-uk (3)
- # clojurescript (27)
- # community-development (2)
- # data-science (1)
- # datahike (2)
- # datomic (11)
- # deps-new (67)
- # emacs (4)
- # graalvm (15)
- # hyperfiddle (11)
- # introduce-yourself (1)
- # lsp (6)
- # malli (30)
- # midje (4)
- # nrepl (13)
- # off-topic (86)
- # polylith (7)
- # releases (2)
- # sql (10)
No. All datomic libraries only run on JVM. Why you want to run datomic on clojurescript? Is possible to access JS/npm ecosystem in Clojure/JVM via #CAJN79WNT polyglot Otherwise, checkout #C68M60S4F and #C87NB2CFN for fullstack solutions
I didn’t know it’s possible to access js/npm via graalvm, i’ll look into it, thanks! 🙏
what are the use cases of Ions? I'm a bit familiar with serverless, but do Ions replace the necessity of a web server? Is it a solution for a scheduled / event-driven scenarios, or also for a web application?
We use Ions to host our web application and it works very nicely in that role. For event-driven tasks Ions provide simple and effective integration with the larger ecosystem through “proxy” lambdas that allow your Clojure code to do all the heavy (business domain) lifting. An area where Ions are weak is when dealing with non-AWS and non-HTTP requests/inputs, notably websockets. Effective websocket solutions I have seen require external termination for the websocket and an independent mechanism for associating websocket handles with proxied requests that you can send to your ion.
Could I ask where one might read more about proxy lambdas and Ions? Could you recommend a resource?
https://docs.datomic.com/cloud/ions/ions-reference.html#lambda-config is a good reference for configuration and https://docs.datomic.com/cloud/ions-tutorial/entry-points.html#invoke-lambda is a tutorial -but I’m not very familiar with it. What is not clear from this documentation (at least to me) is the format of each of the countless event body types when your lambda handler receives it. Ultimately I’ve always been able to back into the format by inferring the shape from map key names and presumably related AWS documentation. Either I’m missing something, or Cognitect never really documented this aspect of Ions’ lambda functionality.