<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ioc on Devops Monk</title><link>https://devops-monk.com/tags/ioc/</link><description>Recent content in Ioc on Devops Monk</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 03 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://devops-monk.com/tags/ioc/index.xml" rel="self" type="application/rss+xml"/><item><title>Spring IoC and Dependency Injection</title><link>https://devops-monk.com/tutorials/spring-boot/spring-ioc-dependency-injection/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://devops-monk.com/tutorials/spring-boot/spring-ioc-dependency-injection/</guid><description>Every Spring Boot application is built on one idea: the framework creates and wires your objects, not you. This article explains how that works and how to use it effectively.
Inversion of Control In traditional Java, you create objects yourself:
// You control the dependencies public class OrderService { private final OrderRepository repository = new JpaOrderRepository(); private final EmailService email = new SmtpEmailService(&amp;#34;smtp.gmail.com&amp;#34;); } Problems:
OrderService is tightly coupled to specific implementations You can&amp;rsquo;t swap JpaOrderRepository for a mock in tests without editing OrderService If SmtpEmailService needs its own dependencies, you must construct those too Inversion of Control (IoC) flips this: instead of creating your dependencies, you declare what you need and let a container provide them.</description></item></channel></rss>