Scopes

Dip provides 4 scopes (or life-time strategies) that you can use to register dependencies:

• The .Prototype scope will make the DependencyContainer resolve your type as a new instance every time you call resolve. It's a default scope.
• The .ObjectGraph scope is like .Prototype scope but it will make the DependencyContainer to reuse resolved instances during one call to resolve method. When this call returns all resolved insances will be discarded and next call to resolve will produce new instances. This scope must be used to properly resolve circular dependencies.
• The .Singleton and .EagerSingleton scopes will make the DependencyContainer retain the instance once resolved the first time, and reuse it in the next calls to resolve during the container lifetime. .EagerSingleton scope makes the DependencyContainer to resolve dependencies registered with this scope when you call bootstrap method.

You specify scope when you register dependency:

container.register() { ServiceImp() as Service } //.Prototype is a default
container.register(.ObjectGraph) { ServiceImp() as Service }
container.register(.Singleton) { ServiceImp() as Service }

Note: .Singleton and .EagerSingleton scopes are not the same as singleton pattern. There will be only one instance of the component registered with these scopes per container. But they will be not shared between containers and you will be able to create another instance manually.

Warning: Make sure that components registered with .ObjectGraph, .Singleton or .EagerSingleton scope are thread-safe or are accessed only from a single thread.