Need help with container?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

golobby
143 Stars 11 Forks MIT License 79 Commits 4 Opened issues

Description

A lightweight yet powerful IoC container for Go projects

Services available

!
?

Need anything else?

Contributors list

GoDoc Build Status Go Report Card Awesome Coverage Status

Container

A lightweight yet powerful IoC container for Go projects. It provides a simple, fluent and easy-to-use interface to make dependency injection in GoLang easier.

Documentation

Required Go Versions

It requires Go

v1.11
or newer versions.

Installation

To install this package, run the following command in the root of your project.

go get github.com/golobby/container

Introduction

GoLobby Container like any other IoC container is used to bind abstractions to their implementations. Binding is a process of introducing an IoC container that which concrete (implementation) is appropriate for an abstraction. In this process, you also determine how it must be resolved, singleton or transient. In singleton binding, the container provides an instance once and returns it for each request. In transient binding, the container always returns a brand new instance for each request. After the binding process, you can ask the IoC container to get the appropriate implementation of the abstraction that your code depends on. In this case, your code depends on abstractions, not implementations.

Binding

Singleton

Singleton binding using Container:

err := container.Singleton(func() Abstraction {
  return Implementation
})

It takes a resolver function which its return type is the abstraction and the function body configures the related concrete (implementation) and returns it.

Example for a singleton binding:

err := container.Singleton(func() Database {
  return &MySQL{}
})

Transient

Transient binding is also similar to singleton binding.

Example for a transient binding:

err := container.Transient(func() Shape {
  return &Rectangle{}
})

Resolving

Container resolves the dependencies with the method

make()
.

Using References

One way to get the appropriate implementation you need is to declare an instance of the abstraction type and pass its reference to Container this way:

var a Abstraction
err := container.Make(&a)
// "a" will be implementation of the Abstraction

Example:

var m Mailer
err := container.Make(&m)
if err != nil {
    panic(err)
}

m.Send("[email protected]", "Hello Milad!")

Using Closures

Another way to resolve the dependencies is by using a function (receiver) that its arguments are the abstractions you need. Container will invoke the function and pass the related implementations for each abstraction.

err := container.Make(func(a Abstraction) {
  // "a" will be implementation of the Abstraction
})

Example:

err := container.Make(func(db Database) {
  // "db" will be the instance of MySQL
  db.Query("...")
})

You can also resolve multiple abstractions this way:

err := container.Make(func(db Database, s Shape) {
  db.Query("...")
  s.Area()
})

Binding time

You can also resolve a dependency at the binding time in your resolver function like the following example.

// Bind Config to JsonConfig
err := container.Singleton(func() Config {
    return &JsonConfig{...}
})

// Bind Database to MySQL err := container.Singleton(func(c Config) Database { // "c" will be the instance of JsonConfig return &MySQL{ Username: c.Get("DB_USERNAME"), Password: c.Get("DB_PASSWORD"), } })

Notice: You can only resolve the dependencies in a binding resolver function that has already bound.

Standalone instance

Container works without any initialization keeping your bindings in the default instance. Sometimes you may want to create a standalone instance for a part of application. If so, create a new instance:

c := container.NewContainer() // returns container.Container
_ = c.Singleton(binding)
_ = c.Make(&resolver)

The rest stays the same. The default container is still available.

Usage Tips

Performance

The package Container inevitably uses reflection in binding and resolving processes. If performance is a concern, you should use this package more carefully. Try to bind and resolve the dependencies out of the processes that are going to run many times (for example, on each request), put it where that run only once when you run your applications like main and init functions.

License

GoLobby Container is released under the MIT License.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.