AWSLambdaJavaAuroraServerlessV2DataApi VS merloc-java

See the example of the "Database Load" bar sliced by SQL statement for our sample application introduced in the part 1 of our article series.

We configured in our [SAM template]((https://github.com/Vadym79/AWSLambdaJavaAuroraServerlessV2DataApi/blob/master/template.yaml) Aurora database cluster to scale from minimal capacity 0.5 to maximal capacity 1 ACU (which is very small database size) in case of the increased load for the cost saving purpose.

Let's look into our sample application and use SAM template to create infrastructure and deploy the application described on the following picture :

In our experiment we'll re-use the application introduced in the part 1 for this which you can find here.

In our experiment we'll re-use the application introduced in the part 1. You can find the source code here. For the executing those experiments we need to deploy the following SAM template template-with-and-without-data-api-and-rds-proxy.yaml by executing sam deploy -t template-with-and-without-data-api-and-rds-proxy.yaml.

We'll focus on the part where Lambda connects through RDS Proxy to Aurora database. As the code sample we will use what we have created as part of the Data API for Amazon Aurora Serverless v2 with AWS SDK for Java series, and the project can be found on my GitHub repository. The relevant part of the Infrastructure as a Code can be found in this AWS SAM template.

In our experiment we'll re-use the application introduced in the part 1 which source code you can find here. There are basically 2 Lambda functions which both respond to the API Gateway requests to store and retrieve product received from the API Gateway from Amazon PostgreSQL Aurora Serverless v2.

which contains the information about the user and user address which will be stored within one transaction in the 2 corresponding separate tables of the PostgreSQL database. In the "Transactional Example" in the READme where I described the creation of those tables and sequences.

To show the database transaction capability I used the same sample application but added the possibility to create the multiple products within HTTP PUT /products request (see the CreateProductsDataApiFunction Lambda definition in the SAM template). The corresponding Lambda function expects the JSON as HTTP body like :

In order to use the new Data API we need include the following dependency to the pom.xml