This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-24
Channels
- # announcements (10)
- # aws-lambda (9)
- # babashka (14)
- # beginners (166)
- # calva (63)
- # chlorine-clover (4)
- # cider (40)
- # cljs-dev (4)
- # clojure (182)
- # clojure-europe (18)
- # clojure-italy (5)
- # clojure-nl (5)
- # clojure-spec (17)
- # clojure-uk (55)
- # clojurescript (11)
- # core-async (12)
- # cursive (23)
- # datascript (5)
- # datomic (19)
- # emacs (4)
- # fulcro (46)
- # graalvm (2)
- # hoplon (2)
- # joker (3)
- # juxt (1)
- # keechma (2)
- # leiningen (20)
- # malli (1)
- # meander (7)
- # nrepl (1)
- # off-topic (72)
- # pedestal (6)
- # re-frame (15)
- # reitit (7)
- # shadow-cljs (34)
- # sql (14)
- # testing (14)
- # tools-deps (11)
- # tree-sitter (1)
- # vim (14)
- # xtdb (19)
- # yada (3)
Here is the Lambda Layer in the Serverless Application Repository https://serverlessrepo.aws.amazon.com/applications/arn:aws:serverlessrepo:us-east-1:209523798522:applications~babashka-runtime. Any feedback welcome. Later Today I'll prapare a detailed instructions on how to use it.
And the source code https://github.com/dainiusjocas/babashka-lambda-layer
are there any big advantages besides startup time? I guess you no longer need to deploy a jar file?
Cold startup time with 128MB is 400ms, Subsequent calls are from 4ms to 120ms, with majority being around 20ms.
Yes, no jars are needed. Also, the deployment package is just a file or two with your script. And when deployment package is smaller than 3MB you can edit it directly in the console.
wow, very cool! going to show this to my team. I am finding more use cases for babashka by the day
cheers 😉
I myself touched babashka only last Friday 😄