Imagine writing an application where you have to create and manage connections with your database system, use Kafka, set up a web server, configure a cache system, and handle JSON serialization and deserialization, among many other components. The amount of work required just to set up these dependencies before starting to develop features that bring real value can be overwhelming. Moreover, maintaining and setting these dependencies across all components of your code can be cumbersome.<\/p>\n\n\n\n
In the past, many developers dealt with this by employing various design patterns such as Factories, Builders, Proxies, Service Locators, reflection, and many other methods. While these helped, components often became tightly coupled and overly knowledgeable about their dependencies.<\/p>\n\n\n\n
Here’s an example of a factory method to deal with dependency creation without Spring:<\/p>\n\n\n
\npublic class PaymentProcessorFactory {\n\n public static PaymentProcessor createService(String type) {\n if (type.equalsIgnoreCase("paypal")) {\n return new PayPalPaymentProcessor();\n } else if (type.equalsIgnoreCase("stripe")) {\n return new StripePaymentProcessor();\n } else {\n throw new IllegalArgumentException("Invalid payment processor type: " + type);\n }\n }\n}\n\n\/\/ Usage\nPaymentProcessor paypalProcessor = PaymentProcessorFactory.createService("paypal");\nPaymentProcessor stripeProcessor = PaymentProcessorFactory.createService("stripe");\n\n\n<\/pre><\/div>\n\n\nWhile this method works, it has limitations. Adding more methods requires changing the code, which makes it tightly coupled and hard to maintain.<\/p>\n\n\n\n
Introducing Spring IoC<\/h2>\n\n\n\n
To address these issues, Spring introduced the Spring IoC (Inversion of Control) container, which is part of the Spring application context.<\/p>\n\n\n
\n@Configuration\npublic class PaymentProcessorConfig {\n\n @Bean\n @ConditionalOnProperty(prefix = "payment", name = "processor", havingValue = "stripe")\n public PaymentProcessor stripePaymentProcessor() {\n return new StripePaymentProcessor();\n }\n\n @Bean\n @ConditionalOnProperty(prefix = "payment", name = "processor", havingValue = "paypal")\n public PaymentProcessor paypalPaymentProcessor() {\n return new PayPalPaymentProcessor();\n }\n}\n\n\n<\/pre><\/div>\n\n\nUnderstanding IoC<\/h2>\n\n\n\n
Each component is a bean. A bean can be an infrastructure bean (like repositories for interacting with databases, Kafka templates for sending messages) or components created by developers to support business rules.<\/p>\n\n\n\n
IoC means Inversion of Control. Instead of a component calling a factory for a Kafka template to send messages, Spring handles this and delivers a fully functional bean to the component. The component no longer needs to know where the bean comes from or how it\u2019s created. It follows the pattern of \u201cdon\u2019t call me, we\u2019ll call you.\u201d The control of those dependencies is no longer handled by the component but managed by Spring IoC.<\/p>\n\n\n\n
This approach reduces coupling and makes it easier to connect application components, making the application more reusable.<\/p>\n\n\n\n
Spring IoC in Action<\/h2>\n\n\n\n
Spring IoC reads your components and configurations (which can be in XML or Java annotations) and provides a ready-to-go application so the developer can start right away focusing on features that bring more value. It creates all beans at runtime when the application starts.<\/p>\n\n\n\n
Spring IoC uses your configurations to set up your beans through properties, providing flexibility over the beans. For example, when setting the payment processor to Stripe:<\/p>\n\n\n
\n\npayment.processor=stripe\n\n\n<\/pre><\/div>\n\n\nThis can be easily changed to PayPal without touching a single line of your application component that calls this dependency.<\/p>\n\n\n\n
Simplified Dependency Usage<\/h2>\n\n\n\n
Using these dependencies becomes straightforward:<\/p>\n\n\n
\n@Component\npublic class CheckoutService {\n\n @Autowired\n private PaymentProcessor paymentProcessor;\n\n public void processCheckout(PaymentDetails details) {\n paymentProcessor.processPayment(details);\n }\n}\n\n\n<\/pre><\/div>\n\n\nFlexibility and Productivity<\/h2>\n\n\n\n
Depending on the changes in your configuration properties (if it does not involve infrastructure changes like changing your database driver), you may not need to recompile and restart your application. Spring can reload the configurations while the application is running.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
Spring IoC makes our lives easier, our applications less coupled and more reusable, and enhances productivity by allowing developers to focus on what matters most.<\/p>\n\n\n\n
If you like Spring make sure to follow me and stay tuned to learn more! Don\u2019t miss out!<\/p>\n\n\n\n
Willian Moya (@WillianFMoya) \/ X (twitter.com)<\/a><\/p>\n\n\n\n