This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-05-30
Channels
- # babashka (7)
- # beginners (25)
- # calva (22)
- # cljs-dev (1)
- # clojure (62)
- # clojure-europe (118)
- # clojure-hamburg (4)
- # clojure-israel (2)
- # clojure-nl (2)
- # clojure-uk (6)
- # clojured (1)
- # clojurescript (23)
- # conjure (11)
- # cursive (3)
- # datomic (14)
- # duct (2)
- # emacs (12)
- # figwheel-main (1)
- # gratitude (1)
- # hyperfiddle (4)
- # joyride (72)
- # lsp (46)
- # luminus (1)
- # malli (1)
- # off-topic (54)
- # pathom (19)
- # polylith (11)
- # releases (2)
- # sci (22)
- # shadow-cljs (4)
- # vim (11)
- # xtdb (52)
I want to do something with kSQLDB and I'm not sure it will work with bb
though that could be my ignorance
So what most people do is I think in this case to reduce cold starts, build a bespoke graalvm binary, or maybe a fork of babashka with ksqldb support. Or make a ksqldb pod.
E.g. for postgres, etc we have pods: https://github.com/babashka/babashka-sql-pods
I'll check that out ... they also have a REST API which I could use from nbb
but it's not as convenient
OK, to summarize: • Bespoke graalvm binary (can be tricky, if you want me to help on a commercial project, I can do some consultancy perhaps) • Pod (will make ksqldb work with any version of bb, more re-usable for anyone if you make it open source) • Add feature flag to bb • Nbb + REST