graalvm-kotlin-native-image-sample VS holy-lambda

I don't have anything public right now but the setup is pretty simple (although I use Gradle with the Kotlin DSL instead of Maven). It's your standard kotlin or java setup that can build a jar with dependencies included, and 1 extra build step to invoke `native-image` from the Graal SDK.

https://github.com/pvorb/graalvm-kotlin-native-image-sample

This is easily accessible via https://github.com/FieryCod/holy-lambda

https://github.com/FieryCod/holy-lambda + free tier may fit your needs. Also support for babashka or scittle in lambdas. Many options. Looks like every provider has caught up to the cloud function space, so aws, azure, digital ocean, maybe even linode. Maybe shop around.

Check https://github.com/FieryCod/holy-lambda. It supports Clojure, babashka and native.

I'm running Clojure code compiled with GraalVM native for AWS Lambda. Cold start times are low and performance is decent enough, even with CE edition. The whole process is reasonably painless through the use of Holy Lambda https://github.com/FieryCod/holy-lambda

Not quite what you were asking for, but I wanted to chip in as another happy Clojure + GraalVM native user.

This is why holy-lambda-ring-adapter was released. An adapter is a part of holy-lambda project and is already used in production. The adapter supports all the holy-lambda custom backends:

During the weekend I was experimenting with AWS Polly (which is a text-to-speech AWS service) and Babashka in order to demonstrate usage of holy-lambda (a micro framework for running Clojure on the AWS Lambda).

It's my first post here announcing holy-lambda https://github.com/FieryCod/holy-lambda. I've resisted posting it for almost two years since it was far from being production-ready software. On the other hand, today, holy-lambda reached version 0.1.45 with some great features and fixes included. It's high time to show this project publicly.