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)

Advantages of JIT injection

This method was designed to address some of the pain points of traditional DI. The advantages listed here are specific to this method and in contrast to other forms of dependency injection. Benefits specific to this method include the following.

Better User Experience (UX) due to fewer inputs—I know I have raised this point a lot, but code that is easier to understand is also easier to maintain and extend. When a function has fewer parameters, it's inherently easier to understand. Compare the constructor:

func NewGenerator(storage Storage, renderer Renderer, template io.Reader) *Generator {
return &Generator{
storage: storage,
renderer: renderer,
template: template,
}
}

With this one:

func NewGenerator(template io.Reader) *Generator {
return &Generator{
template: template,
}
}

In this example, we removed...