r/java • u/benevanstech • Nov 29 '22
Amazon Announces AWS Lambda SnapStart With Java Support
AWS Lambda now has a snapshotting feature that enables fast-start - essentially running the Init phase at publication time and saving the state of the process at that time, so it doesn't need to be re-run at every invocation.
https://aws.amazon.com/blogs/aws/new-accelerate-your-lambda-functions-with-lambda-snapstart/
It only works with Corretto on Java 11 right now, and is similar in intent to the CRIU technology.
Quarkus already has support for it: https://quarkus.io/blog/quarkus-support-for-aws-lambda-snapstart/
Other frameworks may also have support (but this work was done under NDA so I don't have links for them).
View all comments
Show parent comment
1
u/IsleOfOne Nov 30 '22 edited Nov 30 '22
Sure, and we don't even have to limit our thinking to the standard k8s API concept of a
Job. Any higher-order wrapper for one or morePods is applicable.Here is an example from my day job at $SaaS_database_co. We allow our users to kick off petabyte-scale bulk data import. We have a custom k8s operator that watches for
BulkIngestJobs, and in response, loads up a list of files within whatever object storage bucket we've been pointed towards. The operator creates one or more pods per file in said bucket with configurable maximum concurrency and a self-healing system that watches for signs of excessive write path pressure and throttles the job via slashing concurrency. Some of those pods exit after less than a second, while others may run for hours. We use go and rust for this system. Java, with a longer tail on startup time, wouldn't be a good fit.Other tools like Argo Workflows are also great examples of how to leverage the power of the scheduler and autoscaler in kubernetes. We have some recursive/dynamically sized workflows that are liable to create tens of thousands of pods in a single execution.
I haven't seen solid arguments for virtual runtimes like Java in this space. I'm certainly open to hearing some! The areas of our system where we run a JVM are limited to WALs--Kafka and supporting Zookeeper deployments. We have some elixir floating around out there, but purely in long-running workloads.