Spring Boot
AWSLambdaJavaSnapStart | Spring Boot | |
---|---|---|
18 | 168 | |
5 | 73,127 | |
- | 1.0% | |
9.1 | 10.0 | |
9 days ago | 5 days ago | |
Java | Java | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
AWSLambdaJavaSnapStart
-
Spring Boot 3 application on AWS Lambda - Part 4 Measuring cold and warm starts with AWS Serverless Java Container
In the part 2 of the series we introduced AWS Serverless Java Container and in the part 3 we demonstrated how to write AWS Lambda with AWS Serverless Java Container using Java 21 and Spring Boot 3.2. In this article of the series, we'll measure the cold and warm start time including enabling SnapStart on the Lambda function but also applying various priming techniques like priming the DynamoDB invocation and priming the whole web request. We'll use Spring Boot 3.2 sample application for our measurements, and for all Lambda functions use JAVA_TOOL_OPTIONS: "-XX:+TieredCompilation -XX:TieredStopAtLevel=1" and give them all 1024 MB memory.
-
AWS SnapStart - Part 19 Measuring cold starts and deployment time with Java 17 using different Lambda memory settings
In our experiment we'll re-use the application introduced in part 8 for this. Here is the code for the sample application. There are basically 2 Lambda functions which both respond to the API Gateway requests and retrieve product by id received from the Api Gateway from DynamoDB. One Lambda function GetProductByIdWithPureJava17Lambda can be used with and without SnapStart and the second one GetProductByIdWithPureJava17LambdaAndPriming uses SnapStart and DynamoDB request invocation priming. We'll measure cold starts using the following memory settings in MBs : 256, 512, 768, 1024, 1536 and 2048.
-
Spring Boot 3 application on AWS Lambda - Part 3 Develop application with AWS Serverless Java Container
For the sake of explanation we'll use our Spring Boot 3.2 sample application and use Java 21 runtime for our Lambda functions.
-
AWS SnapStart - Part 18 Measuring cold starts with Java 17 using different deployment artifact sizes
Medium Size application with DynamoDB persistence. We'll re-use the application introduced in part 8 for this. There are basically 2 Lambda functions which both respond to the API Gateway requests and retrieve product by id received from the API Gateway from DynamoDB. One Lambda function can be used with and without SnapStart and the second one uses SnapStart and DynamoDB request invocation priming. There are bunch of dependencies declared in pom.xml like aws-lambda-java-core, aws-lambda-java-events, slf4j-simple, crac, dynamodb and url-connection-client. The deployment size of such application is 15 MB.
-
Spring Boot 3 application on AWS Lambda - Part 2 Introduction to AWS Serverless Java Container
and others will be a part of a separate project and therefore also used without the usage of the all other AWS Serverless Java Container APIs only for purpose of mocking the API Gateway Request/Response (i.e. for Priming). I've already used them for Priming requests for Quarkus and Micronaut frameworks. Dependency to the AWS Serverless Java Container was included by default for the Micronaut on AWS Lambda SnapStart Priming example and needed to be added explicitly for the Quarkus on AWS Lambda SnapStart Priming example only to implement web request priming. We'll make use of these abstractions in one of our subsequent articles when we'll discuss cold and warm start time improvements for Spring Boot 3 application on AWS Lambda using AWS Lambda SnapStart in conjunction with priming techniques.
-
AWS SnapStart - Part 16 Measuring cold and warm starts with Java 21 using different asynchronous HTTP clients
Using the asynchronous DynamoDBClient means that we'll be using the asynchronous programming model, so the invocation of getItem will return CompletableFuture and this is the code to retrieve the item itself (for the complete code see)
-
AWS SnapStart - Part 15 Measuring cold and warm starts with Java 21 using different synchronous HTTP clients
Let's figure out how to configure the HTTP Client. There are 2 places to do it : pom.xml and DynamoProductDao
-
AWS SnapStart - Part 13 Measuring warm starts with Java 21 using different Lambda memory settings
In our experiment we'll re-use the application introduced in part 9 for this. There are basically 2 Lambda functions which both respond to the API Gateway requests and retrieve product by id received from the API Gateway from DynamoDB. One Lambda function GetProductByIdWithPureJava21Lambda can be used with and without SnapStart and the second one GetProductByIdWithPureJava21LambdaAndPriming uses SnapStart and DynamoDB request invocation priming. We'll measure cold and warm starts using the following memory settings in MBs : 256, 512, 768, 1024, 1536 and 2048. I also put the cold starts measured in the part 12 into the tables to see both cold and warm starts in one place. The results of the experiment below were based on reproducing more than 100 cold and approximately 100.000 warm starts for the duration of our experiment which ran for approximately 1 hour. Here is the code for the sample application. For it (and experiments from my previous article) I used the load test tool hey, but you can use whatever tool you want, like Serverless-artillery or Postman. Abbreviation c is for the cold start and w is for the warm start.
-
AWS SnapStart - Part 11 Measuring cold starts with Java 21 using different deployment artifact sizes
Small HelloWorld-style application which consists of Lambda receiving the APIGateway request with product id and basically prints this id out. There is no persistence layer involved. The application is that simple, that there is now priming to be applied. There are only several dependencies declared in pom.xml like aws-lambda-java-core and slf4j-simple. The deployment artifact size of such application is 137 KB only.
-
Measuring Lambda cold starts with AWS SnapStart - Part 8 Measuring with Java 17
For measurement purposes I created/copied the sample application and configured Lambda functions to use Java 17 runtime for Lambda and 1024 MB memory .
Spring Boot
- JHipster 8 - Analisando o código da nossa primeira aplicação monolítica - Parte 2/3
-
Walmart is migrating the remaining F# code into Java
- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...
I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.
- AI PR adds auto generated comments to whole Spring Boot Project
-
AI commented the entire Spring Boot codebase
https://github.com/spring-projects/spring-boot/pull/39754/co...
-
Spring Boot 3 And Java 17 Migration Guide
If you’re currently running with an earlier version of Spring Boot, I recommend that you upgrade to Spring Boot 2.7 before migrating to Spring Boot 3.0. It minimizes compatibility issues as much as possible.
- Spring Boot 3.2.0 Release Notes
-
The Game of Life, the Universe, and Everything: Java Virtual Threads in Action
Okay, we need to build the game? No problem, we will use Spring Boot and Swing!
-
Netflix Uses Java
It's weird that some people including you directly attack my competence. As a power user you should have plenty of experience getting something to work that is not properly document, does not work how the documentation promised it to, or has weird problems on top of it. Look at idiotic things like this:
https://github.com/spring-projects/spring-boot/issues/33044
Take any similar issue and you'll see a bunch of people who try to find a solution for them because they just aren't repeatable at all. The underlying issue is the auto configuration doing things you can't follow quite properly. It's like it wasn't mean to be understood. Issues like the one I linked above also show me that the spring dev crowd also doesn't understand the ecosystem anymore. The problem is complexity and automagic.
-
What's New in Spring Framework 6.1
An interested reader can decide for themselves:
https://github.com/spring-projects/spring-boot/tree/main/spr...
-
Secure Java URL encoding and decoding
Explicitly decoding URL query parameters occurs less often because many frameworks, including Spring Boot, handle decoding automatically.
What are some alternatives?
serverless-java-frameworks-samples
helidon - Java libraries for writing microservices
serverless-java-container - A Java wrapper to run Spring, Spring Boot, Jersey, and other apps inside AWS Lambda.
Play - The Community Maintained High Velocity Web Framework For Java and Scala.
Hey - HTTP load generator, ApacheBench (ab) replacement
javalin - A simple and modern Java and Kotlin web framework [Moved to: https://github.com/javalin/javalin]
Quarkus - Quarkus: Supersonic Subatomic Java.
spring-native - Spring Native is now superseded by Spring Boot 3 official native support
Jooby - The modular web framework for Java and Kotlin
aws-sdk-java-v2 - The official AWS SDK for Java - Version 2
ZK - ZK is a highly productive Java framework for building amazing enterprise web and mobile applications