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 application in the same aws-lambda-java-25-dynamodb-as-container-image GitHub repository, which we can deploy on AWS Lambda as a container image. Besides the previous part, please read the following articles in this series to grasp the general concepts:

Part 3 Introducing Lambda SnapStart

Part 4 SnapStart and DynamoDB request priming

Part 5 SnapStart and full priming

The business logic required to implement the Lambda SnapStart priming approaches and the measurement design is the same.…