This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-07
Channels
- # 100-days-of-code (13)
- # beginners (12)
- # business (6)
- # cider (6)
- # cljdoc (9)
- # cljs-dev (1)
- # cljsrn (4)
- # clojars (4)
- # clojure (31)
- # clojure-dev (12)
- # clojure-uk (11)
- # clojurescript (16)
- # cursive (1)
- # datascript (4)
- # datomic (10)
- # editors (1)
- # figwheel-main (3)
- # graphql (10)
- # lein-figwheel (29)
- # off-topic (1)
- # pedestal (1)
- # re-frame (31)
- # reitit (3)
- # shadow-cljs (27)
- # slack-help (5)
- # spacemacs (1)
- # yada (5)
I’ve got an app which I would like to prototype with Datomic Cloud Ions. Though it is a chat not so I’m curious what the cold start/latency story is like. I’m having trouble finding information regarding this. Datomic Ions may not be suitable which is fine but if it is ok then I would prefer to use it.
The startup time is good. Clojure isn't run on the lambda, it runs in the auto scaling group, the lambda is a lightweight rpc proxy.
Could you explain what the rpc proxy is, like the work it is doing? I’m still learning all of this.
@U09LZR36F btw thanks for responding. Was thinking there is little activity in here and would go without a response
I shouldn't have said rpc. I made that bit up, I meant to say "it acts as an rpc". Basically you can think of it as doing a HTTP request to your auto-scaling group, forwarding on the data that went to the lambda to your asg.
Chat bot haha