Spring Tips: Go Further and Faster with Spring Boot 3.3 (Updated)

HEY! This is the SECOND upload of a video that had errors. Don't watch that one. Watch THIS one!
Hi, Spring fans! In this installment we look at ways to make your applications go further, faster, with AppCDS, GraalVM, AOT on the JRE, and Project CRaC (coordinate restore at checkpoint)
#springboot #java #graalvm #programming #coding

[@Vityoube]

Josh, thanks for informative video! I am getting used to 'elevator music' in ptojects ( to run one project it was necessary to wait for 1,5 minutes for dev mode, the other one required 6 minutes, the third one -- although it was based on microservices approach -- required to wait for one hour for one microservice). What performance do you expect from the mentioned appraches for real life projects (like financial services, governmental services and others)? I wonder if Java developers will have the startup time for their application comparable to some JS frameworks -- where even heavy project is up and running after 5-10 seconds

[@TonyObermeit]

That was fascinating and informative. Learned heaps. Would have been interesting if you'd applied the same type of timing check on the get all dogs method. I'd like to understand the difference each of those options AOT, AppCDS and GraalVM would have on post startup operations.

[@davidkpidiba8591]

Thank you for the video

[@RickDkkrd]

Thanks for the video, very informative as always. One correction: you wanted to never init the db, but set spring.sql.init.mode to "always" instead of "never"

[@svenqnerd1338]

Thanks for the video. I think something went wrong cutting the video around the implementation of the Lifecyle around 26:30. ;)

[@aleksandr_format]

Will it work with the same smoothie if an application has huge custom configuration properties amount? Like an property which enabling something or disabling some bunch of beans in the application

[@razatech22]

What's AtomicReference? Since it's final then how it's setting another value inside main method

[@Boss-gr4jw]

Issue with these technologies is that they are far from production ready. I haven't yet seen a project which even uses Spring Native. The moment you have to start coding in hints and flags to compile something this will never be adopted.

[@prashoo]

Most of the prod apps are still running java8. How u can expect them to use native?

[@Boss-gr4jw]

@@prashoo That is not the concern. The issue is that setting up native build for real production app requires too much effort. Old legacy apps will never be candidate for this anyway, so pointing this out has nothing to do with the situation. This can only be applied to hello world projects with 0 dependencies or only few dependencies which have all those predefined hints, but I cannot imagine regular developer having to spend time writing compiler hints to get their feature working.

[@cloudsquall88]

This kind of performance at the start is kinda laughable if the database lives on the pc

[@hamzasalihu]

Hi Josh, I got stuck here!
mvn clean package -DskipTests
[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:3.3.1:process-aot (process-aot) on project myservices: Process terminated with exit code: 1 -> [Help 1]
Java 21
I believe I am doing something wrong, please help.