/explore
|
You are here 
|
blog.separateconcerns.com | ||
| | | | |
fusectore.dev
This is the first part in a series of articles on dependency injection for the play framework using guice. As soon as Ive written the next part, it will be linked here. Please note that while the examples are written in Scala, the principles apply for Java likewise. Furthermore, please be aware that Guice is not the only framework to do dependency injection with. It is probably the most prominent one in the play ecosystem though. Guice does so called runtime dependency injection. This means dependencies ... |
|
| | | | | ||
| | | | |
solnic.dev
I was wondering what do we, rubyists, think about dependency injection these days as I remember some discussions about it which were mostly lots of post-java-trauma type of criticism. I had this blog post in the back of my head for a long time but knowing that this subject was sort of...explored... |
|
| | | | | ||
| | | | |
mikemikina.com
Vapor 3 has a very interesting dependency injection framework which will help you manage dependencies and mock them inside your tests. |
|
| | | | | ||
| | | | |
blog.theamazingrando.com
The point of this post isn't to convince you of the usefulness of Dependency Injection there's been plenty of pixels spilled about it already. Instead, I want to talk about using Dry::Container to alleviate some of the pain points that DI introduces. |
|
| | | |||
