Clojurians Log v2
Clojure programming
Channels
Apps
babashka
Georgiy Grigoryan 2025-08-15T07:26:38.720829Z
Hi. It seems next.jdbc and postgres JDBC driver were added and then removed from the binary. Probably due to graal vm issues and binary size?
Is this still relevant: To compile babashka with the next.jdbc library and a PostgresQL driver:
$ export BABASHKA_FEATURE_JDBC=true
$ export BABASHKA_FEATURE_POSTGRESQL=true
$ script/uberjar
$ script/compile
I intend to use bb on aws lambda with blambda and wondering whether it's better to use the PostgreSQL pod.
borkdude 2025-08-15T07:28:22.364049Z
@geodrome that was only for one very old version a long time ago. I decided to remove it because postgres isn't the only db in the world and image size indeed. The pod is an option. Compiling your own bb is also an option. I haven't tested those flags in a while, but if there's any problems let me know
Georgiy Grigoryan 2025-08-15T07:29:14.750539Z
@borkdude Thank you very much. Leaning towards using the pod. Seems less likely to cause an issue.
Georgiy Grigoryan 2025-08-15T07:30:12.157639Z
Especially since I am not sure if if blambda will play nice with a custom bb binary.
borkdude 2025-08-15T07:31:08.421719Z
Great. Also, if you're open to using Node.js you could try #nbb or #squint. For nbb I've written a post here: https://blog.michielborkent.nl/aws-lambda-nbb.html In nbb you can use any npm dependency you want, opposed to bb where Java libs must be baked in (this is where pods come in)
Georgiy Grigoryan 2025-08-15T07:51:15.243019Z
I've considered nbb, but just don't wanna deal with the async programming model.
borkdude 2025-08-15T07:51:53.192309Z
👍