---
title: "Comment by Shai Almog on \"Spring  Inversion of control & Dependency Injection\" | Hashnode"
description: "Nicely said. While I like Spring a lot, I&#39;m not a huge fan of IoC because it makes failures harder to deal with. E.g. if a resource fails to load/inject the"
url: "https://hashnode.com/posts/spring-inversion-of-control-and-dependency-injection/6175cdfd0f452c1cd94fbca1/comment/61760a217a94bb0be56751e2"
---

[Discussion](https://hashnode.com/posts/spring-inversion-of-control-and-dependency-injection/6175cdfd0f452c1cd94fbca1)

Comment [Spring Inversion of control & Dependency Injection](https://hashnode.com/posts/spring-inversion-of-control-and-dependency-injection/6175cdfd0f452c1cd94fbca1)

[Shai Almog](https://hashnode.com/@talktotheduck)

[Oct 25, 2021](https://hashnode.com/posts/spring-inversion-of-control-and-dependency-injection/6175cdfd0f452c1cd94fbca1/comment/61760a217a94bb0be56751e2)

Nicely said. While I like Spring a lot, I'm not a huge fan of IoC because it makes failures harder to deal with. E.g. if a resource fails to load/inject the error messages are just unreadable.

But once it does work it's pretty cool. You can write simple objects that ignore most of the complex questions like "which database am I using" and "on which machine is it located". You can define defaults in the configuration and you can easily override them in production.
