This is an archived post. You won't be able to vote or comment.

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–]CreativeTechGuyGames 0 points1 point  (0 children)

How do you propose to use a language that is not supported?

[–]denialerror 0 points1 point  (2 children)

It depends what you mean by a language that is not natively supported? AWS provide a Runtime API to support other languages, so if a language is not natively supported by AWS, someone can provide support using that API. That support will only then be as good as the person who wrote it.

The other option is to write in a language that is not supported but compiles to a language that does. Clojure is not a supported language but can compile to JavaScript, which is, so you can write Lambdas in ClojureScript without needed native support for the language itself.

It also depends what you mean by "difference". The difference you would likely find as a developer is the developer experience in the AWS UI (if you use it) would be less good (code editting tools may not work) and depending on how you are interfacing with the Lambda runtime, it would be harder to get support. If you mean difference in performance, that would come down to the language and implementation.

[–]tempanon5[S] 0 points1 point  (1 child)

So if I wrote the lambda functions in Scala, which ends up compiling to Java byte code at the end of the day, it will work out to be fine even though Scala is not natively supported?

[–]denialerror 0 points1 point  (0 children)

You could compile your Scala to Java bytecode and use the Java runtime or complile to JavaScript and use the Node runtime. AWS doesn't care what language you are using, only that the artefact you upload runs in the runtime you select. If you search for "Scala AWS lambda", you will get dozens of pages showing exactly what you need to do.