Dependency Injection with Go

Re:Dependency Injection with Go by fishnchips on Monday July 28, 2014 @08:23AM (#8096283)

I honestly don't think there even was a problem to be solved. Constructors could just accept their dependencies (interfaces) as parameters.

[ Parent | on HN ]

Re:Dependency Injection with Go by shellac on Monday July 28, 2014 @08:51AM (#8096385)

On larger code bases it can help a lot. You get to a point where you need that config object over in some random function and you start weaving it through constructors. At which point a simple DI system really appeals.

DI code also tends to be more pleasant to test in my experience since it promotes loose coupling.

[ Parent | on HN ]

Re:Dependency Injection with Go by fishnchips on Monday July 28, 2014 @10:36AM (#8096954)

I believe there are other ways:

http://commandcenter.blogspot.com/2014/01/self-referential-f...

And you should probably avoid situations where you suddenly need config objects in 'random places'. This could be a symptom of chaotic API design. But then again, whatever works for you.

[ Parent | on HN ]

Re:Dependency Injection with Go by ExpiredLink on Monday July 28, 2014 @10:29AM (#8096891)

Quite the contrary as repeatedly experienced in Java land.

[ Parent | on HN ]