Fork me on GitHub

I don't get the AWS Lambda idea ... doesn't Lambda start up a new container for each request? Or run a new command for each? Isn't that the worst possible thing with Clojure for JVM?


Hopefully I'm just unaware of some Lambda features.


Ok, dived into the docs and now understand it a bit better. The container instance may stick around for a bit, but should still be stateless.


@hlship yeah it sticks around for a while, depending on request rate


You'd still be quite vulnerable to high startup latency


Also, AFAICT each request runs in a separate container, so if you have spikes in concurrency, they will either wait in line, or fire up another container


@hlship if you have some time, I recently watched this talk[1] and found it quite informative. The TL;DR is that containers are snapshot and are long-lived, a @danielcompton said, and can be reclaimed and restarted after some time - no matter what. [1]:


@hlship @andrewhr @danielcompton We will soon be able to choose Pedestal in CLJ or CLJS. Using CLJ on Lambda does suffer from startup time but throughput under load is better. CLJS starts up fast but doesn’t handle the same volume.


So for bursty workload or low-volume apps, CLJS is going to be better. For continuous workload CLJ will be more cost effective and have higher throughput.

mitchelkuijpers17:07:51 Is there any reason this is not merged? This currently prevents me from using vase 😞


apparently websocket support is not good enough, does any one know how can I get the session in the on-text callback ?


I hit some similar problems w.r.t. the way you set up web sockets. I hope to submit a PR that opens it up a bit for approaches that don't quite match what the current code supports. See and for my approach.


Can I use pedestal router with a pure ring application ?