This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-21
Channels
- # announcements (4)
- # aws (29)
- # aws-lambda (1)
- # babashka (21)
- # beginners (143)
- # calva (47)
- # cider (31)
- # clj-kondo (24)
- # cljsrn (4)
- # clojure (70)
- # clojure-australia (3)
- # clojure-czech (1)
- # clojure-europe (97)
- # clojure-greece (4)
- # clojure-nl (3)
- # clojure-uk (45)
- # clojurescript (70)
- # code-reviews (1)
- # conjure (7)
- # cursive (10)
- # datomic (13)
- # duct (5)
- # emacs (1)
- # fulcro (38)
- # graalvm (1)
- # graphql (9)
- # honeysql (13)
- # integrant (33)
- # jobs (14)
- # jobs-rus (1)
- # malli (7)
- # off-topic (72)
- # pathom (1)
- # re-frame (11)
- # reitit (9)
- # remote-jobs (2)
- # sci (11)
- # shadow-cljs (9)
- # sql (5)
- # tools-deps (5)
- # xtdb (6)
would be simpler than setting up a Graal clj or java project. might be worth the perf tradeoff
Something like this? https://serverlessrepo.aws.amazon.com/applications/arn:aws:serverlessrepo:us-east-1:209523798522:applications~babashka-runtime
exactly like that. I’ll need to update it to get the latest bb with aws pods but that’s great.
Make sure to force downloading the pod so it's already available in the docker image
it's downloaded to $HOME/.babashka so you'd have to copy that dir inside the image after you call load-pod
New Docker runtime stuff should make it pretty easy to use bb in Lambda, no more layers etc
It boils down to doing a GET to get the args, and POST-ing the result: https://docs.aws.amazon.com/lambda/latest/dg/runtimes-api.html
@lukaszkorecki Is that similar to this one? https://serverlessrepo.aws.amazon.com/applications/arn:aws:serverlessrepo:us-east-1:209523798522:applications~babashka-runtime Or is it even easier now?
I notice he's doing some requests in this namespace similar to what you describe: https://github.com/dainiusjocas/babashka-lambda-layer/blob/ddec711dcb261eb1fa2798da45c060c0112b3887/src/lambda/impl/runtime.clj#L6
I think this is based on the "old" way of providing custom runtimes for Lambda, now you "just" build a container image and bundle whatever files and tools you need. The "layers" approach had some limitations in terms of size and what you can actually ship
but, that namespace does look handy - I think AWS just opened up all the nitty gritty of how Lambdas are put together by introducing Docker support