How would one do dependency injection in scala?

Question

I\'m still at the beginning in learning scala in addition to java and i didn\'t get it how is one supposed to do DI there? can or should i use an existing DI library, should it

Answer 1

I have shown how I created a very simple functional DI container in scala using 2.10 here.

Answer 2

A recent project illustrates a DI based purely on constructor injection: zalando/grafter

What's wrong with constructor injection again?

There are many libraries or approaches for doing dependency injection in Scala. Grafter goes back to the fundamentals of dependency injection by just using constructor injection: no reflection, no xml, no annotations, no inheritance or self-types.

Then, Grafter add to constructor injection just the necessary support to:

• instantiate a component-based application from a configuration
• fine-tune the wiring (create singletons)
• test the application by replacing components
• start / stop the application

Grafter is targeting every possible application because it focuses on associating just 3 ideas:

• case classes and interfaces for components
• Reader instances and shapeless for the configuration
• tree rewriting and kiama for everything else!

Answer 3

Standard Java DI frameworks will usually work with Scala, but you can also use language constructs to achieve the same effect without external dependencies.

Answer 4

Previous posts covered the techniques. I wanted to add a link to Martin Odersky's May 2014 talk on the Scala language objectives. He identifies languages that "require" a DI container to inject dependencies as poorly implemented. I agree with this personally, but it is only an opinion. It does seem to indicate that including a DI dependency in your Scala project is non-idiomatic, but again this is opinion. Practically speaking, even with a language designed to inject dependencies natively, there is a certain amount of consistency gained by using a container. It is worth considering both points of view for your purposes.

https://youtu.be/ecekSCX3B4Q?t=1154

Answer 5

I haven't done so myself, but most DI frameworks work at the bytecode level (AFAIK), so it should be possible to use them with any JVM language.

Answer 6

In addition to the answer of Dan Story, I blogged about a DI variant that also uses language constructs only but is not mentioned in Jonas's post: Value Injection on Traits (linking to web.archive.org now). This pattern is working very well for me.