How to Deploy Scala Code to AWS Lambda - a Tutorial | Rock the JVM

[@MrRobmango]

Thanks for the introduction to lambda! I need to write one of these soon. Surprised how simple it is.

[@viddyasagarverma3722]

Thanks for another wonderful tutorial on Scala.

[@01loicd]

Very useful thanks!

[@expacz2506]

very good content on your channel as well as udemy course on Scala, great job!

[@rockthejvm]

Thanks!!

[@kevalan1042]

Thanks, interesting tutorial. Why is Java 8 preferred?

[@rockthejvm]

Java 8 is getting a bit old. You can also use newer JDKs.

[@ForestHensley]

Excelente! Gracias.

[@alexperit]

How actually call this AWS lambda from the Scala code through REST API ? Since it is not useful to have it just for manual performing

[@fredysierra]

man.. great content!

[@rockthejvm]

Glad you like it! More incoming!

[@UCTNX4PiSl496AhgUyGlB5wg]

How you are debugging this ?

[@daniellopes6874]

Billed 1300ms, that is why the JVM should be avoided as the backend for a Lambda function. JVM cold start times are horrible. Does the time improve if you repeat the requests, do they keep the JVM hot for repeated calls at least for a certain amount of time? Could you look into GraalVM and retry with the compiled (to native?) code :-)?

[@rockthejvm]

This is a really interesting point - I'll do a comparison in a future video. Also, being naive (thought it was obvious), the video did not have a warning that running code on AWS costs money (only a little, but still). Added the warning into the description.

[@UCTNX4PiSl496AhgUyGlB5wg]

Although Scala is powerful functional programming language, spring cloud functions with AWS adaptor on Graal VM will be game changer.

[@daniellopes6874]

There are better suited (and easier to learn) languages like python, javascript (node), go and rust. So I doubt the game changing. But I am biased as I do not like the spring vendor lockin and the way spring does its magic things with reflection and a gazillion annotations.

[@matteocossu3535]

I agree that running JVM on Lambda is not ideal, but not always a bad choice. When dealing with multiple requests around the same time, often the same JVM instance is reused. We can use this also to keep in memory objects between different calls of the same function. At the moment, AWS also offers "Provisioned Concurrency" to provision lambdas in advance (at a cost) and reduce cold-start problem. Using this, some people are even launching heavy stuff like Spring Boot. Maybe this example is too extreme, but I wouldn't say that we should never use JVM for Lambda :)

[@msp767]

@@rockthejvm did you ever do that follow-up video?