Symfony’s DependencyInjection component is a PHP implementation of a Service Container, or as others like to call it, a Dependency Injection Container (DIC).
The component also provides useful tools for handling service definitions, like XML loaders or dumpers.
If you want to learn more about the dependency injection or the dependency injection container, read an excellent series of articles on the subject by Fabien Potencier: What is Dependency Injection?
Note: Code used in this post is available on github: https://github.com/jakzal/SymfonyComponentsExamples
We will also need Buzz, a lightweight HTTP client. It’ll serve us as an example service. Config component is needed for one of the code snippets.
git clone https://github.com/symfony/DependencyInjection.git vendor/Symfony/Component/DependencyInjection git clone https://github.com/symfony/Config.git vendor/Symfony/Component/Config git clone https://github.com/symfony/ClassLoader.git vendor/Symfony/Component/ClassLoader git clone https://github.com/kriswallsmith/Buzz.git vendor/Buzz
Symfony ClassLoader component will take care of the class autoloading (read more about it in the ”Autoloading classes in an any PHP project with Symfony2 ClassLoader component”).
Following code is sufficient to load classes from an any Symfony component (assuming components are put into the vendor/Symfony/Component directory):
<?php // src/autoload.php require_once __DIR__.'/../vendor/Symfony/Component/ClassLoader/UniversalClassLoader.php'; $loader = new Symfony\Component\ClassLoader\UniversalClassLoader(); $loader->registerNamespaces(array( 'Symfony' => __DIR__.'/../vendor', 'Buzz' => __DIR__.'/../vendor/Buzz/lib', 'PSS' => __DIR__ )); $loader->register();
Creating objects, the usual way
To create a Browser object and fetch content from google we could write the following piece of code:
$browser = new \Buzz\Browser(); $response = $browser->get('http://www.google.com');
By default Buzz uses FileGetContents as a client (which is a wrapper for file_get_contents() PHP function). Imagine new requirements came and forced us to use curl.
It’s possible with Buzz. We just need to pass the client explicitly to the Browser:
$client = new \Buzz\Client\Curl(); $browser = new \Buzz\Browser($client); $response = $browser->get('http://www.google.com');
After a while we noticed that our calls are often timed out. Default timeout of 5 seemed to be not sufficient so we increased it to 15:
$client = new \Buzz\Client\Curl(); $client->setTimeout(15); $browser = new \Buzz\Browser($client); $response = $browser->get('http://www.google.com');
Notice that code needs to be modified in all the places the Browser was used. It soon becomes a maintenance hell. Copy&Paste is not the best way for re-usability ;) Just imagine effort needed to change the connection timeout when you create the browser in ten places. Or changing the client. What if you forget one?
We might create factory for the Browser. However, writing factories for all our services breaks DRY principle as we end up writing classes with a similar purpose.
One of the solutions is to centralize the object creation. Dependency Injection Container (DIC) does just that.
Note: Dependency Injection Container is also called a Service Container. Thinking about objects managed by the container as services, better reflects the purpose of the container.
Creating objects with DIC
Instead of creating Browser object explicitly, we’ll just tell the container how to do it:
<?php // dependencyinjection.php require_once __DIR__.'/src/autoload.php'; use Symfony\Component\DependencyInjection\ContainerBuilder; use Symfony\Component\DependencyInjection\Definition; $serviceContainer = new ContainerBuilder(); $browserDefinition = new Definition('Buzz\Browser'); $serviceContainer->setDefinition('browser', $browserDefinition);
And then ask it for the service:
$browser = $serviceContainer->get('browser'); $response = $browser->get('http://www.google.com/');
To replace the default HTTP client with Curl we might define another service and pass it to the browser as a reference:
<?php // dependencyinjection.php // ... $serviceContainer = new ContainerBuilder(); $clientDefinition = new Definition('Buzz\Client\Curl'); $clientDefinition->addMethodCall('setTimeout', array(15)); $serviceContainer->setDefinition('browser.client', $clientDefinition); $browserDefinition = new Definition('Buzz\Browser', array(new Reference('browser.client'))); $serviceContainer->setDefinition('browser', $browserDefinition);
Notice that even though object creation becomes more and more complicated we manage it in one place.
On the other hand, every time we want to use a browser all we need to do is to get it from the container:
$browser = $serviceContainer->get('browser');
Service consumers are not affected by the service definition changes.
Another nice thing is that service won’t be created unless we requested it.
Using XML to describe services
Services can be defined in many formats, not just PHP. Yaml and XML seem to be most convinient and readable ones. Symfony DependencyInjection component gives us tools to dump and load service definitions into the container with ContainerBuilder.
Moving service definitions to the configuration stored in Yaml or XML files has several advantages.
First of all we’re creating even clearer separation between an object creation and the code which uses it.
Secondly, service definitions are more readable.
Following XML file describes the same services we defined in PHP before:
<?xml version="1.0" encoding="utf-8"?> <-- config/buzz.xml --> <container xmlns="http://symfony.com/schema/dic/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://symfony.com/schema/dic/services http://symfony.com/schema/dic/services/services-1.0.xsd"> <services> <service id="browser.client" class="Buzz\Client\Curl"> <call method="setTimeout"> <argument>15</argument> </call> </service> <service id="browser" class="Buzz\Browser"> <argument type="service" id="browser.client"/> </service> </services> </container>
Loading the service definitions into the container is fairly simple. We need to create a CotnainerBuilder and pass it to an XmlFileLoader which will do all the work for us:
<?php // dependencyinjectionloader.php require_once __DIR__.'/src/autoload.php'; use Symfony\Component\DependencyInjection\ContainerBuilder; use Symfony\Component\DependencyInjection\Loader\XmlFileLoader; use Symfony\Component\Config\FileLocator; /** * Loading services */ $serviceContainer = new ContainerBuilder(); $loader = new XmlFileLoader($serviceContainer, new FileLocator(__DIR__.'/config')); $loader->load('buzz.xml'); /** * Using services */ $browser = $serviceContainer->get('browser'); $response = $browser->get('http://www.google.com/');
The opposite works equally well. To dump service definitions into an XML we need to pass ContainerBuilder instance to the XmlDumper:
<?php // dependencyinjection.php // ... use Symfony\Component\DependencyInjection\Dumper\XmlDumper; $dumper = new XmlDumper($serviceContainer); echo $dumper->dump();
Note: In a real life scenario we’d probably maintain our service definitions in XML or YML file(s) but dump them to PHP with PhpDumper for performance reasons.
Visualizing the services
In complex application services and relations between them might become, well… complex. GraphvizDumper might be handy in such situations as it lets us to present the services on a graph.
<?php // dependencyinjectiongraphviz.php require_once __DIR__.'/src/autoload.php'; use Symfony\Component\DependencyInjection\ContainerBuilder; use Symfony\Component\DependencyInjection\Dumper\GraphvizDumper; use Symfony\Component\DependencyInjection\Loader\XmlFileLoader; use Symfony\Component\Config\FileLocator; $serviceContainer = new ContainerBuilder(); $loader = new XmlFileLoader($serviceContainer, new FileLocator(__DIR__.'/config')); $loader->load('buzz.xml'); $dumper = new GraphvizDumper($serviceContainer); echo $dumper->dump();
To actually generate a graph we will need a dot program (from graphviz). Once we dump the result of our script into a services.dot file we can easily convert it to an image:
dot -Tpng -o services.png services.dot
The result should look similar to the following picture.