In‑Depth Explanation of Spring Boot Startup Sequence and Extension Points

Java developers often focus on CRUD, but to integrate middleware with Spring they must understand the framework's startup mechanics; this article provides a comprehensive guide.

A long diagram (referenced in the original) visualizes the exact order in which Spring initializes beans, processes aware interfaces, runs post‑processors, and triggers lifecycle callbacks.

Eleven probing questions are posed to test knowledge of Spring’s integration points, covering RPC registration, MQ consumer groups, Tomcat port opening, and the timing of traffic entry points.

The article describes a real‑world fault where Kafka consumers begin processing before Spring has finished initializing, leading to null‑pointer errors because event listeners are not yet registered; the root cause is starting traffic in the init-method phase.

Answers clarify the execution order of PostConstruct , afterPropertiesSet , and init-method , explain that bean initialization order is not guaranteed without @Order , and confirm that Autowired injection occurs before PostConstruct , preventing null pointers.

A code experiment defines TestSpringOrder implementing interfaces such as ApplicationContextAware , BeanFactoryAware , InitializingBean , SmartLifecycle , ApplicationListener<ContextRefreshedEvent> , CommandLineRunner , and SmartInitializingSingleton , with each method logging its execution.

The resulting log output demonstrates the precise sequence, starting with BeanFactoryPostProcessor , followed by bean construction, aware callbacks, BeanPostProcessor hooks, PostConstruct , afterPropertiesSet , init-method , bean post‑processing, @Bean method execution, SmartInitializingSingleton , SmartLifecycle#start , ContextRefreshedEvent , and finally CommandLineRunner .

Key extension points are enumerated: BeanFactoryAware , ApplicationContextAware , BeanNameAware , ApplicationListener , CommandLineRunner , SmartLifecycle#start , @PostConstruct , InitializingBean , init-method , BeanPostProcessor , BeanFactoryPostProcessor , among others.

To avoid the earlier fault, the article recommends opening HTTP, RPC, and MQ entry traffic only after SmartInitializingSingleton or the SmartLifecycle start phase, when all singleton beans and event listeners are fully ready.

In conclusion, Spring Boot only exposes the embedded web server after the entire application context is ready, so developers should register services and enable traffic at the appropriate lifecycle hooks to ensure reliable startup.