Auto Configuration

🔍 What Is It?

Auto-configuration is a set of @Configuration classes that Spring Boot activates conditionally based on what's on your classpath, what beans you've already defined, and what properties you've set.

How Spring Boot discovers auto-configurations:

• →Spring Boot 2.x: META-INF/spring.factories file
• →Spring Boot 3.x: META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports

Key conditional annotations:

• →@ConditionalOnClass — activate only if a class is on the classpath
• →@ConditionalOnMissingBean — activate only if you haven't defined your own bean
• →@ConditionalOnProperty — activate only if a property is set
• →@ConditionalOnWebApplication — activate only in web apps
• →@ConditionalOnExpression — activate based on SpEL expression

This means auto-configuration is never forced on you — define your own bean and Spring backs off.

🎯 Why Do We Need It?

Without auto-configuration, every Spring Boot project would require:

@Bean
public DataSource dataSource() {
    HikariDataSource ds = new HikariDataSource();
    ds.setJdbcUrl("jdbc:postgresql://localhost:5432/mydb");
    // ... 10 more lines
    return ds;
}
// Plus EntityManagerFactory, TransactionManager, etc.

Auto-configuration does all this from spring.datasource.* properties. You write 3 lines of config instead of 50 lines of code.

🏗️ What Happens in Real Projects?

Every Spring Boot application uses auto-configuration constantly:

• →Add spring-boot-starter-web → DispatcherServlet, Jackson, Tomcat auto-configured
• →Add spring-boot-starter-data-jpa + DB driver → DataSource, JPA, Transactions auto-configured
• →Add spring-boot-starter-security → Security filter chain auto-configured

In enterprise projects, teams write custom auto-configurations for shared libraries that auto-configure themselves when added as a dependency.

⚙️ How It Works

Step-by-step auto-configuration process:

1. @EnableAutoConfiguration triggers AutoConfigurationImportSelector
2. Selector reads AutoConfiguration.imports — a list of 150+ configuration classes
3. Each config class is evaluated against its @Conditional annotations
4. Passing configs are imported into the ApplicationContext
5. @ConditionalOnMissingBean ensures your beans take priority

Debug auto-configuration:

debug=true
# Or: GET /actuator/conditions

💻 Example

Understanding and Customizing Auto-Configuration — How to inspect, override, and write your own auto-configuration.

@Configuration
public class DataSourceConfig {

    // Your custom DataSource takes priority over auto-configuration
    @Bean
    @Primary
    public DataSource primaryDataSource(
            @Value("${db.primary.url}") String url,
            @Value("${db.primary.username}") String username,
            @Value("${db.primary.password}") String password) {

        HikariConfig config = new HikariConfig();
        config.setJdbcUrl(url);
        config.setUsername(username);
        config.setPassword(password);
        config.setMaximumPoolSize(20);
        config.setMinimumIdle(5);
        config.setConnectionTimeout(30000);
        return new HikariDataSource(config);
    }
}

🤔 Common Confusions

🚨 Common Production Issues

✅ Best Practices

🏛️ Architect's Note

💬 Frequently Asked Questions

🎯 Key Takeaways

🔗 Related Topics

🎯 Practice this topic in interviews

↗ Where this topic fits