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)

Monkey magic!

Monkey patching is changing a program at runtime, typically by replacing a function or variable.

While this is not a traditional form of dependency injection (DI), it can be used in Go to facilitate testing. In fact, monkey patching can be used to test in ways that are otherwise impossible.

Let's consider a real-world analogy first. Let's say you want to test the effects of a car crash on the human body. You probably wouldn't be volunteering to be the human that was in the car during testing. Nor are you allowed to make changes to the vehicle to facilitate your testing. But you could swap out (monkey patch) the human for a crash test dummy during your test.

The same process holds true for monkey patching in code; the changes only exist during the test and in many cases can be applied with little impact on the production code. 

A quick note for...