# Binder Introduction

![](https://3413979917-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LA-UVvsc-e1GVkiaPQ-%2F-LA-Ud03e_n2SeqLC9Ls%2F-LA-UqbfNRKCKVEPyQFh%2FbinderIntro_WireBoxBinder.jpg?generation=1523648000009396\&alt=media)

In all reality we could be building our objects and its dependencies, [object graph](http://en.wikipedia.org/wiki/Object_graph), without any configuration just plain **location** and **implicit** conventions. This is great but not very flexible for refactoring, so let's do the best practice of defining a mapping or an alias to a real object.

We do this by creating a WireBox configuration binder `wirebox.system.ioc.config.Binder`, which is a simple CFC that defines the way WireBox behaves and defines object mappings. This binder is then used to initialize WireBox so it has knowledge of these mappings and our settings.

{% hint style="info" %}
The Binder is also the way you configure WireBox for operation.
{% endhint %}