Quarkus 3 application on AWS Lambda- Part 10 Measuring Lambda cold and warm starts with REST API application

Measurements of cold and warm start times of our application In Part 8 , we learned how to develop a pure Quarkus REST application and deploy it on AWS Lambda. For the preparation of my talk about developing Serverless Java REST applications on AWS using frameworks such as Quarkus, I found time to measure the performance of the Lambda function with the different approaches (see below). I refer to my articles where we didn't use the Quarkus REST controllers directly, but the pure AWS Lambda functions, to see how we implemented the SnapStart and priming approaches. They look completely the same when using Quarkus REST controllers. No SnapStart. Please read the article Introduction to the sample application and first Lambda performance measurements . SnapStart enabled, but no priming applied. Please read the article Reducing Lambda cold starts with Lambda SnapStart . SnapStart enabled, and DynamoDB request priming applied. Please read the article Reducing Lambda cold starts with SnapStart