Contribute to help us improve!
Are there edge cases or problems that we didn't consider? Is there a technical pitfall that we should add? Did we miss a comma in a sentence?
If you have any input for us, we would love to hear from you and appreciate every contribution. Our goal is to learn from projects for projects such that nobody has to reinvent the wheel.
Let's collect our experiences together to make room to explore the novel!
To contribute click on Contribute to this page on the toolbar.
A good starting point for understanding DI is https://en.wikipedia.org/wiki/Dependency_injection.
In spring the reference documentation explains the dependency injection (DI) aka Inversion of Control (IoC) mechanisms in deep details: https://docs.spring.io/spring-framework/docs/current/reference/html/core.html#beans-introduction
A more practical guide can be found here: https://www.baeldung.com/inversion-control-and-dependency-injection-in-spring and more topics around DI here: https://www.baeldung.com/spring-dependency-injection
For quarkus the following article explains the details of dependency injection: https://quarkus.io/guides/cdi-reference
Use annotations over xml for controlling DI
Some frameworks like spring might still allow Bean definitions via XML. This should be avoided and instead the annotations should be used.
Use constructor injection
Constructor injection makes the code better testable, because dependencies can be mocked without using reflection techniques.