Fork me on GitHub
#aws
<
2018-01-04
>
ghadi01:01:21

anyone here deploy to lambda but not AOTed?

qqq01:01:15

how would that work? lambda loads up clojureinterpreter on every function invocation?

ghadi01:01:57

you could have a java method that implemented the right interface, with a static initializer that resolved the proper var, once.

ghadi01:01:23

(clojure doesn’t have an interpreter, btw)

qqq01:01:19

so whenever a lambda container is created, during the initialiaztion step, the clojure compiler is loaded

qqq01:01:32

then at every function call, it recompiles your clojure code and runs it ?

qqq01:01:48

what flexibility does this buy you over AOT ?

ghadi02:01:57

slow down, that’s not what I meant.

ghadi02:01:27

when the lambda deployment is spun up, it calls a single class that calls the clojure compiler once.

qqq02:01:51

are you saying: 1. at container creation time: load clojure compiler, compile clojure code 2. at each function call, invoke already-compiled bytecode ?

qqq02:01:03

if so, what additional flexibility does this gain over plain AOT ?