The second of two articles about AWS Lambda SnapStart, this looks at how developers can update their existing Java Lambda applications to use SnapStart, and what performance improvements they might expect to see.
At reInvent 2022 AWS announced “SnapStart” - a new Lambda capability to drastically improve cold starts when using Lambda with Java, or other JVM languages.
AWS Lambda is my preferred runtime environment for cloud-based code. Lambda has gained many, many, features over the eight years since it was launched. Most of these are focussed on the Lambda runtime - more CPUs, more memory, different CPU architectures, many more language runtimes, custom runtimes, integration with approximately a bajillion other services, etc.
Welcome to Part 2 of “Starting with CDK” . In Part 1 I helped you prepare your environments for CDK, as well as deploy and examine your first CDK application.
This is a cross-post from the Cockroach Labs blog. Cockroach Labs have been kind enough to sponsor our book Programming AWS Lambda, which you can download for free from the Cockroach Labs website.
Simple, single-responsiblity, AWS Lambda applications have one Lambda function and one event source. You might use API Gateway to provide a simple HTTP-callable interface to a Lambda function.
AWS Cloud Development Kit (CDK) has become, in its short history, a very popular infrastructure-as-code tool. It’s not too surprising why - it allows engineers to use richer programming languages to define infrastructure, rather than having to use JSON or YAML.
