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 7, Dependency Injection with Method Injection

1. What are the ideal use cases for method injection?

Method injection is great for the following:

  • Functions, frameworks, and shared libraries
  • Requesting scoped dependencies, such as context or user credentials
  • Stateless objects
  • Dependencies that provide context or data in the request and as such are expected to vary between calls.

2. Why is it important not to save dependencies injected with method injection?

Because the dependency is a parameter of the function or method, every call will supply a new dependency. While saving the dependency before calling other internal methods might seem more straightforward than passing the parameter around as a dependency, such practice will cause data races between multiple concurrent usages.

 

3. What happens if we use method injection too much?

This question is somewhat subjective...