A Spring Boot service takes 45 seconds to start, causing slow autoscaling. How do you improve it?
Short answer
Profile startup (Spring's ApplicationStartup / actuator startup endpoint, JFR) to find slow beans and blocking initializations, remove unnecessary auto-configuration and classpath scanning, make heavy initialization lazy or asynchronous, use class data sharing or AOT caches, consider GraalVM native images or CRaC where suitable, and size containers so CPU is not throttled at startup.
Detailed answer
- Measure:
spring.main.lazy-initializationexperiments,/actuator/startup(BufferingApplicationStartup), JFR. - Common culprits: eager DB migrations on large schemas, remote calls during bean init, large classpath scanning, Hibernate metadata for many entities, CPU limits too low (JIT starved).
- Fixes: lazy init for non-critical beans, async warm-up, AppCDS / Java 24+ AOT cache, Spring Boot CDS support, native image for small services or functions, CRaC checkpoints, higher CPU request during startup, readiness probes that reflect warm-up.
What the interviewer expects
Measurement, knowledge of modern JVM startup features, and container considerations.
Common mistakes to avoid
Disabling health checks to "fix" slow startup.