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)

Summary

In this chapter, we examined the state and quality of our sample service after applying DI, and contrasted that with its original state, thereby reminding ourselves both why we made the changes, and what we gained from making them.

We took one final look at our dependency graph to get a visual perspective on just how well we managed to decouple our packages.

We also saw how our sample service was both significantly easier to test, and that our tests were much more focused after making our changes.

At the end of the chapter, we also discussed how to approach starting a new service and how DI can help with that endeavor too.

With that, we have finished our examination of DI for Go. Thank you for taking the time to read this book—I hope that you have found it both pragmatic and useful.

Happy coding!