Introduction
In part 8 of the series, we learned how to convert the sample application to one using a container image as a deployment artifact on AWS Lambda and measured the performance of the Lambda functions. We observed that the Lambda cold start times are quite high.
In this part, we'll enable SnapStart on the Lambda functions using a container image . We'll also apply priming techniques and measure the performance of the Lambda functions for all scenarios.
You can find the final version of our sample applications, which we can deploy on AWS Lambda as a container image, in the following GitHub repositories:
Sample application with JDBC and Hikari connection pool in the aws-lambda-java-25-aurora-dsql-as-container-image repository.
Sample application with Hibernate and Hikari connection pool in the aws-lambda-java-25-hibernate-aurora-dsql-as-container-image repository.
Besides the previous part, please read the following articles in this series to grasp the general concepts:
Part 3 Introducing…