Clojurians Log v2

@cfleming: again from memory and based on a few unscientific observations, but it seemed like a new JVM was started and the lambda function handler instantiated

@ragge: Interesting, thanks. It looks like CLJS is actually probably a better fit for Lambda since Node is first class there, but I haven’t tried it yet.

@cfleming: i think it will depend a lot on your usage patterns, but yeah, generally quick startup might be a win

@ragge: Right. I have one Lambda function right now that I need the JVM for because I’m using encryption (it’s just Java), but I think for most future things I’ll try CLJS first.

Lambda is pretty cool actually, I have a lot of use cases I can use it for.

The API gateway mapping is a gigantic pain, though.

@cfleming: yeah, that too me seems like a poor re-invention of an ESB

@cfleming: but I really like the unit of execution with lambda, don't want to care about instances if i don't have to

@ragge: Right, it’s perfect for a lot of use cases.

@mskomrak has joined the channel

@dottedmag has joined the channel

@christianromney has joined the channel

@ragge: Once those few minutes are up, do they then trash the instance so you’re paying the 1s startup with Clojure again, or do they serialise the JVM state somehow?