AWS Lambda SnapStart for Java Applications

[@mezagun53]

Hello I tried Snapstart as in the video, but after 15 minutes, when I trigger the api again, the spring starts up again. Why ?

[@serverlessjames]

When you invoked the function did you invite the alias or the $LATEST version. I made this mistake at first, but you need to make sure you invoke against the alias as that is where the snapshot is taken

[@mezagun53]

@@serverlessjames thank you for answering. I paid particular attention to the alias issue. It isn't happening. Do I need to make another setting on aws or does snapstart become disabled after a certain time?

[@DanielLpz1]

Nice video, I have a question regarding the snapstart initialization attempts, I can see there are around 6 logs printed and some of them were successfully initialized, why is it trying multiple times? Is there any way to initialize the snapstart just once?

[@serverlessjames]

Great question Daniel. This is correct, and happens because Lambda takes the snapshots across different availability zones in parallel.

[@DanielLpz1]

@@serverlessjames thanks for your reply.

[@HarryManchanda]

❤️

[@victorpacheco3107]

[@brunofsleite]

Hello James, excellent videos, I like so much your channel. Could you please tell me how I can create a serverless aurora v2? Is it too complicated to adapt the code?

[@serverlessjames]

Thankyou 👌 do you mean connecting a Java application to a database running on Aurora serverless v2?

[@brunofsleite]

@@serverlessjames In this video series you created the database using cdk, right? Using the PostgreSQL engine. would it be possible to use PostgreSQL serverless aurora V2 in the same code that you used to create the infrastructure?

[@arghyamitra3281]

I think if u use spring boot 3 or graalvm with Java startup time is very very less without this lambda feature

[@serverlessjames]

Thanks for the comment. SpringBoot 3 requires Java17 which isn't currently available in Lambda. You could run it as a custom runtime but that need a lot of work. In terms of GraalVM, Quarkus has a great blog comparing native images to SnapStart. Performance is comparable, with SnapStart just about coming in faster. However, enabling SnapStart is as simple as turning it on. GraalVM native images have a more complex build process quarkus.io/blog/quarkus-support-for-aws-lambda-snapstart/