We Began to Forget: Demystifying Spring Framework

We began to forget how to pass parameters to functions. Before @Bean, before @Configuration or @PropertySource and certainly way before WebSecurityConfigurerAdapter objects were responsible not only for their own behaviour, but also for creating everything they depended on. public class OrderService { private final PaymentProcessor processor; public OrderService() { this.processor = new StripePaymentProcessor(); } } This code works, but it also quietly locks many decisions inside the class, because OrderService now decides which payment processor is used, how it is created, and when its lifecycle starts, and once this happens, changing that decision means changing the code itself. Configuration and behaviour start to mix, breaking single responsibility principle.