Summary
After looking at a number of the options out there for implementing Dependency Inversion Principle (DIP) in go, there seems to be two obvious options.
The first is using Inversion of Control (IoC), and as we have seem the basics are there in the base code. It can also be seen that extending this to include features such as configuration driven binding is very possible.
The other option is Dependency Injection (DI), however of the three packages we have looked at, it looks from my viewpoint that only one is straightforward enough to use, and is probably the one best positioned to be extended.
In future posts I will look into extending these two approaches, hopefully producing two complete processes for implementing DIP in go.
If you would like to download and try the samples used in these posts please check out the following git repo: commentsondev
<< Previous: depinject
The first is using Inversion of Control (IoC), and as we have seem the basics are there in the base code. It can also be seen that extending this to include features such as configuration driven binding is very possible.
The other option is Dependency Injection (DI), however of the three packages we have looked at, it looks from my viewpoint that only one is straightforward enough to use, and is probably the one best positioned to be extended.
In future posts I will look into extending these two approaches, hopefully producing two complete processes for implementing DIP in go.
If you would like to download and try the samples used in these posts please check out the following git repo: commentsondev
<< Previous: depinject
Links
Dependency Inversion in Go - IntroductionDependency Inversion in Go - Simple IoC
Dependency Inversion in Go - go-inject
Dependency Inversion in Go - go.inject
Dependency Inversion in Go - depinject
Dependency Inversion in Go - Summary
No comments:
Post a Comment