https://devops-monk.com/tags/auto-configuration/Recent content in Auto-Configuration on Devops MonkHugoen-usSun, 03 May 2026 00:00:00 +0000https://devops-monk.com/2026/05/spring-boot-auto-configuration-deep-dive/Sun, 03 May 2026 00:00:00 +0000https://devops-monk.com/2026/05/spring-boot-auto-configuration-deep-dive/“Spring Boot is magic” is something you hear a lot. Add spring-boot-starter-data-jpa and suddenly you have a working DataSource, a JpaTransactionManager, and a LocalContainerEntityManagerFactoryBean — without writing a single @Bean method. Understanding how this actually works turns the magic into a tool you can control, debug, and extend. The Entry Point: @EnableAutoConfiguration @SpringBootApplication is a shorthand for three annotations: @Configuration @EnableAutoConfiguration // this is the one that matters here @ComponentScan public class MyApplication { public static void main(String[] args) { SpringApplication.https://devops-monk.com/tutorials/spring-boot/spring-boot-auto-configuration/Sun, 03 May 2026 00:00:00 +0000https://devops-monk.com/tutorials/spring-boot/spring-boot-auto-configuration/Spring Boot “just works” — you add a dependency and things appear in your application context. This article explains exactly how that happens, so you can debug it when it doesn’t, and extend it when you need to. What Auto-Configuration Actually Does When you add spring-boot-starter-data-jpa to your project, you don’t write a single line of config — yet Spring creates a DataSource, EntityManagerFactory, and JpaTransactionManager automatically. That’s auto-configuration. Auto-configuration is a set of @Configuration classes that Spring Boot ships.