This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-15
Channels
- # announcements (13)
- # aws (6)
- # babashka (23)
- # babashka-sci-dev (6)
- # beginners (64)
- # calva (110)
- # cider (25)
- # cljs-dev (5)
- # cljsrn (8)
- # clojars (5)
- # clojure (20)
- # clojure-austin (1)
- # clojure-europe (77)
- # clojure-nl (1)
- # clojure-uk (3)
- # clojurescript (14)
- # cursive (7)
- # datahike (9)
- # datomic (13)
- # eastwood (15)
- # emacs (14)
- # figwheel-main (1)
- # fulcro (8)
- # graalvm-mobile (2)
- # graphql (2)
- # honeysql (2)
- # hyperfiddle (2)
- # introduce-yourself (4)
- # jobs (4)
- # joyride (4)
- # leiningen (4)
- # lsp (8)
- # minecraft (8)
- # off-topic (11)
- # polylith (18)
- # rdf (2)
- # reagent (3)
- # reitit (4)
- # remote-jobs (1)
- # shadow-cljs (12)
- # specter (7)
- # xtdb (3)
What people are using these days to create and deploy AWS Lambda? I used https://github.com/dainiusjocas/babashka-lambda a while ago, but the repo is not maintained and automation is pretty basic. I heard about Holy Lambda recently, what is your experience?
We just build a JAR and deploy it using Terraform, our Lambdas are used only for infrastructure stuff so they don't change that often
HL is quite minimal and ships with the great performance. It's faster than running Clojure on official Java runtime consume less memory.
The current pain points are the HL tasks that are planned to get rewritten in few weeks / months depending on my mood :D