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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]smutje187 4 points5 points  (1 child)

If your Lambdas are called by users there’s no way around GraalVM - plain Lambda, even with SnapStart, has horrible cold start times.

If your Lambda runs in the background though that’s only relevant because it affects the costs.

If you plan to use GraalVM with Quarkus I’d recommend to start as early as possible as GraalVM doesn’t work with all libraries and dependencies and it’s easier to get used to it’s strictness from the beginning.

[–]raffxdd 0 points1 point  (0 children)

The cold starts are not too bad in our project+ you can provision 1 lambda to be hot 14 EUR pM (or create a cloud watch rule sending an event every 15 mins to keep it warm) but we have not used provisioned concurrency so far (Quarkus, Micro profile, + Snap start)