A binder is a simple class that registers bindings to the container for a particular area of your domain. For example, you might have a binder called UserBinder to centralize all the bindings related to your user domain.

use Aphiria\DependencyInjection\Binders\Binder;
use Aphiria\DependencyInjection\IContainer;

final class UserBinder extends Binder
    public function bind(IContainer $container): void
        $container->bindInstance(IUserRepository::class, new UserRepository());
        $container->bindSingleton(IUserService::class, UserService::class);

Prior to handling a request, you can dispatch all your binders:

$binders = [new UserBinder()];

foreach ($binders as $binder) {

// Your app is all set

Although this is simple, it's probably a little heavy-handed to register all your bindings for each request when only a few will be needed to handle a request. The next section will go into more details on how to handle this more optimally.

Lazy Dispatching

Rather than having to dispatch every binder on every request, you can use LazyBinderDispatcher to lazily dispatch them, eg only when they're actually needed. At a high level, it looks inside your binders to determine what each of them bind and resolve. It then sets up a factory for each of those bindings that calls Binder::bind() only when at least one of the binder's bindings is used. This prevents you from having to list out the bindings a binder registers to get this sort of functionality (like other frameworks force you to do).

Let's build on the UserBinder from the previous example and set up our app to lazily dispatch it:

use Aphiria\DependencyInjection\Binders\LazyBinderDispatcher;
use Aphiria\DependencyInjection\Binders\Metadata\Caching\FileBinderMetadataCollectionCache;
use Aphiria\DependencyInjection\Container;

$container = new Container();
$metadataCache = getenv('ENV_NAME') === 'production'
    ? new FileBinderMetadataCollectionCache('/tmp/binderMetadataCollectionCache.txt')
    : null;
$binderDispatcher = new LazyBinderDispatcher($metadataCache);
$binderDispatcher->dispatch([new UserBinder], $container);

That's it. Now, whenever we call $container->resolve(IUserService::class), it will automatically run UserBinder::bind() once and use the binding defined inside to resolve it every time after. Additionally, any binder that resolves interfaces bound by UserBinder will also be dispatched.

Note: It's recommended that you only use caching for production environments. Otherwise, changes you make to your binders might not be reflected.

Using Application Builders

The configuration library provides helper methods to simplify building your application, including registering your binders. Refer to its documentation to learn more about it.