Spring Boot "fat" JAR: The Thin Parts of a Thick Artifact
summary
Examines Spring Boot’s “fat” JAR packaging: how the fat JAR is implemented, its classloading model, startup-time and JDK tool conflicts, and differences between dev/test/prod modes. Explains when fat JARs are appropriate or problematic (especially for container deployments) and suggests alternatives and deployment considerations for production Spring Boot applications.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 6:09Fat JAR explained
- 14:20ClassLoader issues
- 26:27Startup speed impact
- 33:30Optimizing for Docker
- 44:49Layered JAR benefits
- 54:42Buildpacks vs Jib
- 1:07:57Summary
related talks
42mCrafting the Ultimate Docker Image for Spring Applications
48mA Practical Guide to Containerizing Your Spring Boot Application
35mOptimize your applications to the max with Jakarta EE and MicroProfile
46mDockerfiles, Buildpacks, Jib and more, best way to run Java code in Containers?
51mBootiful Spring Boot 3.x
24mSpring: Your Next Java Micro-Framework
43mStep up the performance game with Spring Boot and Project Leyden
49mLean Spring Boot Applications for the Cloud