Understanding Spring Boot Auto‑Configuration Mechanism

Spring Boot has become an essential skill for developers and interview candidates, offering a convention‑over‑configuration approach that simplifies project setup by integrating many popular third‑party libraries.

The framework uses a global configuration file, either application.properties or application.yml , where common properties such as server.port and logging.level.* can be defined and later referenced in the code.

Auto‑configuration logic resides in the spring-boot-autoconfigure‑x.x.x.x.jar . The key entry point is the @EnableAutoConfiguration annotation, which is included in the composite @SpringBootApplication annotation. When the application starts, @EnableAutoConfiguration triggers AutoConfigurationImportSelector.selectImports() , which uses SpringFactoriesLoader.loadFactoryNames() to scan all META-INF/spring.factories files on the classpath and collect the fully‑qualified names of auto‑configuration classes.

Each auto‑configuration class (named *AutoConfiguration ) is conditionally loaded based on a set of Spring conditional annotations, such as @ConditionalOnBean , @ConditionalOnMissingBean , @ConditionalOnClass , @ConditionalOnMissingClass , and @ConditionalOnProperty . These annotations ensure that a configuration is applied only when the required beans, classes, or properties are present (or absent).

For example, ServletWebServerFactoryAutoConfiguration is responsible for creating the embedded web server. It is annotated with @EnableConfigurationProperties(ServerProperties.class) , which imports the ServerProperties bean. The @ConfigurationProperties annotation on ServerProperties binds values from the global configuration file (e.g., server.port=8081 ) to the bean, allowing the embedded Tomcat server to use the specified port.

In summary, Spring Boot’s auto‑configuration works by loading a list of *AutoConfiguration classes declared in spring.factories , applying them conditionally, and binding configuration properties to dedicated *Properties beans via @ConfigurationProperties . Understanding this flow helps developers both in practical development and in answering interview questions about the framework.