Hands-On Dependency Injection in Go

Interpreting the dependency graph

Like a lot of things in the programming world, what a dependency graph says is very much open to interpretation. I use the graph to discover potential problems that I can then go searching for in the code.

So, what would a perfect graph look like? If there were one, it would be very flat, with pretty much everything hanging from the main package. In such a system, all of the packages would be completely decoupled from each other and would have no dependencies beyond their external dependencies and the standard library.

This is really not feasible. As you will see with the various DI methods in the second part of this book, the goal is frequently to decouple the layers so that dependencies flow only in one ...