Book Image

Hands-On Dependency Injection in Go

By : Corey Scott
Book Image

Hands-On Dependency Injection in Go

By: Corey Scott

Overview of this book

Hands-On Dependency Injection in Go takes you on a journey, teaching you about refactoring existing code to adopt dependency injection (DI) using various methods available in Go. Of the six methods introduced in this book, some are conventional, such as constructor or method injection, and some unconventional, such as just-in-time or config injection. Each method is explained in detail, focusing on their strengths and weaknesses, and is followed with a step-by-step example of how to apply it. With plenty of examples, you will learn how to leverage DI to transform code into something simple and flexible. You will also discover how to generate and leverage the dependency graph to spot and eliminate issues. Throughout the book, you will learn to leverage DI in combination with test stubs and mocks to test otherwise tricky or impossible scenarios. Hands-On Dependency Injection in Go takes a pragmatic approach and focuses heavily on the code, user experience, and how to achieve long-term benefits through incremental changes. By the end of this book, you will have produced clean code that’s easy to test.
Table of Contents (15 chapters)

Chapter 10, Off-the-Shelf Injection

1. When adopting a dependency injection framework, what can you expect to gain?

This, of course, differs significantly between frameworks, but typically, you can expect to see the following:

  • A reduction in boilerplate code
  • Less complexity in setting up and maintaining the dependency creation order


2. When evaluating a dependency injection framework, what kind of issues should you being looking out for?

Beyond the gains mentioned previously, my primary criterion is the effect it has on the code; putting it a different way, whether I like how the code looks after adopting the framework.

I would also consider the configurability of the framework itself. Some configuration is expected, but too much can lead to a complicated UX.

The last aspect to consider is the health of the framework project. Is it being actively maintained? Are...