No experience yet but you may also want to ask there too #holy-lambda. BTW Lambdas can now expose URLs without having to be fronted by API Gateway, so they're even easier to expose than before.

Remember that you've got million(s) of free Lambda calls per month (I suppose it's for small-sized CPU and RAM ones). Looks like it's really worth checking out.

Thanks Daniel, i don't need to expose this to a public endpoint/url as it will only need to make http calls then send an email. It's good to know there are free calls per month.

I've been itching for an excuse to try holy lambda’s babashka backend. If you do end up going the holy lambda route I'd love to see an experience report!

@drewverlee I think the easiest option for you is HL on the custom Java17 Layer, since: • your use case doesn't require a fast startup time, • going with GraalVM would be an overkill for now since this is another tool you have to learn about. This repository contains a ready-to-go template with mentioned above configuration. In the future, you can always "easily" migrate to the Native backend with this.

https://github.com/FieryCod/holy-lambda-on-java-17

What is cool about this layer is it enables TieredCompilation=1 by default and by that speeding the startup time significantly. https://aws.amazon.com/blogs/compute/increasing-performance-of-java-aws-lambda-functions-using-tiered-compilation/

thanks Karol, i'm taking a look now

Cool!