Lean Spring Boot Applications for The Cloud
summary
Benchmarks use the Spring PetClinic (H2) built with Buildpacks; baseline measures a 4.3s startup, 359MB image and ~302MB initial RAM. Applying Spring AOT, appCDS (Buildpacks-enabled CDS training run), lazy beans, removal of Actuator and unused starters via depclean Maven plugin, plus jlink or alternate JVMs (OpenJ9, GraalVM) halves startup, reduces image size roughly 50% and cuts memory ~30% while keeping throughput comparable; virtual threads improve latency on very small CPU quotas.
AI-written summary · about
chapters (20)
- 0:00Introduction and speaker intro
- 1:23Why optimize Spring Boot apps
- 3:11Cloud challenges for Spring Boot
- 5:20Pet Clinic setup and baseline
- 9:13Build packs for containerization
- 13:05Startup time analysis tools
- 14:07Benchmarking methodology
- 16:17Java version upgrades impact
- 18:02Java optimizations with build packs
- 22:00Spring Boot optimizations
- 26:59Ahead-of-time compilation
- 30:51Application-level optimizations
- 35:06Customizing the JVM runtime
- 37:57AppCDS for faster startup
- 40:24Alternative JVM runtimes
- 43:14Alpine-based builders
- 44:20GraalVM native images
- 46:31Virtual threads benefits
- 47:16Summary of optimizations
- 50:28Q&A and closing
related talks
48mLean Spring Boot Applications for the Cloud
46mLean Spring Boot Applications for The Cloud
39mHow to Reduce the Footprint of Your Spring Boot Applications
24mSpring: Your Next Java Micro-Framework
42mSupercharge your JVM performance with Project Leyden and Spring Boot
42mCrafting the Ultimate Docker Image for Spring Applications
01h 03mBootiful Spring Boot 3
38mBootiful Spring Boot 3