Understanding Spring Boot Auto‑Configuration Mechanism

Spring Boot has become a must‑know skill for developers, and its auto‑configuration mechanism is key to rapid application development.

The global configuration file can be application.properties or application.yml , where properties such as server.port and logging.level.* are defined and documented in the official reference.

Auto‑configuration classes reside in the spring-boot-autoconfigure-x.x.x.x.jar . The @SpringBootApplication annotation includes @EnableAutoConfiguration , which uses AutoConfigurationImportSelector to call SpringFactoriesLoader.loadFactoryNames() and scan all META-INF/spring.factories files on the classpath.

Each entry in spring.factories maps the key EnableAutoConfiguration to a comma‑separated list of xxxxAutoConfiguration classes. These classes are imported as JavaConfig beans when their conditional annotations (e.g., @ConditionalOnBean , @ConditionalOnMissingBean , @ConditionalOnClass , @ConditionalOnMissingClass , @ConditionalOnProperty ) are satisfied.

For example, ServletWebServerFactoryAutoConfiguration is enabled by @EnableConfigurationProperties(ServerProperties.class) . The @ConfigurationProperties annotation binds properties from the configuration file to a ServerProperties bean, which is then registered in the Spring container.

In summary, Spring Boot starts by locating all auto‑configuration classes via @EnableAutoConfiguration , loads them conditionally, and binds external configuration to strongly‑typed property beans, allowing developers to focus on business logic rather than extensive manual setup.