Understanding the Spring Boot Auto‑Configuration Mechanism

Spring Boot has become an essential skill for developers and interviewees, and mastering its auto‑configuration mechanism provides a significant advantage in both work and interview scenarios.

The core of auto‑configuration is triggered by the @SpringBootApplication annotation, which includes @EnableAutoConfiguration . This annotation delegates to AutoConfigurationImportSelector , whose selectImports() method uses SpringFactoriesLoader.loadFactoryNames() to scan all META-INF/spring.factories files in the classpath.

Each spring.factories entry maps the EnableAutoConfiguration key to a list of XXXAutoConfiguration classes. During SpringApplication.run(...) , these classes are loaded into the Spring container as JavaConfig beans.

Auto‑configuration classes are activated only when specific conditions are met, expressed through conditional annotations such as @ConditionalOnBean , @ConditionalOnMissingBean , @ConditionalOnClass , @ConditionalOnMissingClass , and @ConditionalOnProperty .

For example, ServletWebServerFactoryAutoConfiguration uses @EnableConfigurationProperties(ServerProperties.class) to import a bean that binds properties from application.properties (e.g., server.port ) via @ConfigurationProperties . The bound ServerProperties bean is then available to the auto‑configuration class, allowing the configured port to override the default Tomcat value.

In summary, when Spring Boot starts, @EnableAutoConfiguration discovers all auto‑configuration classes listed in spring.factories , loads them, and each class obtains its required settings from corresponding XXXProperties beans that are populated from the global configuration file.

This flow enables developers to customize behavior through simple property entries without writing explicit configuration code.