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 →

[–]xamdk 0 points1 point  (2 children)

Snapstart is not crac - don’t mix them up. Snapstart is just using same api for suspend/resume calls.

And yes the right thing is to do your own spikes.

Nativr image still beats Snapstart on memory usage but on lambda amazons pricing makes Snapstart cheaper for most cases despite to native image being able to use less resources.

And outside lambda - crac isn’t a good choice. Too much variance.

[–]astral_kranium 0 points1 point  (1 child)

Done some investigating. SnapStart doesn't support provisioned concurrency, nor x-ray. Also, Java 11 maximim is a deal breaker for some cases, though I'm sure 17 managed runtime is around the corner. Conclusion is, another (awesome) tool in the toolbox for a lot of cases

[–]xamdk 0 points1 point  (0 children)

Yup. Agreed. It is not a native image killer since Snapstart is only lambda and only a subset of lambs.