Lazy ServicesEdit this page
Warning: You are browsing the documentation for Symfony 3.4, which is no longer maintained.
Read the updated version of this page for Symfony 6.3 (the current stable version).
Another way to inject services lazily is via a service subscriber.
Why Lazy Services?
In some cases, you may want to inject a service that is a bit heavy to instantiate,
but is not always used inside your object. For example, imagine you have
NewsletterManager and you inject a
mailer service into it. Only
a few methods on your
NewsletterManager actually use the
but even when you don't need it, a
mailer service is always instantiated
in order to construct your
Configuring lazy services is one answer to this. With a lazy service, a
"proxy" of the
mailer service is actually injected. It looks and acts
just like the
mailer, except that the
mailer isn't actually instantiated
until you interact with the proxy in some way.
Lazy services do not support final classes.
In order to use the lazy service instantiation, you will first need to install
$ composer require ocramius/proxy-manager
If you're not using the full-stack framework, you also have to install the ProxyManager bridge
$ composer require symfony/proxy-manager-bridge
You can mark the service as
lazy by manipulating its definition:
1 2 3 4
# app/config/services.yml services: AppBundle\Twig\AppExtension: lazy: true
1 2 3 4 5 6 7 8 9 10 11
<!-- app/config/services.xml --> <?xml version="1.0" encoding="UTF-8" ?> <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 https://symfony.com/schema/dic/services/services-1.0.xsd"> <services> <service id="AppBundle\Twig\AppExtension" lazy="true"/> </services> </container>
1 2 3 4 5
// app/config/services.php use AppBundle\Twig\AppExtension; $container->register(AppExtension::class) ->setLazy(true);
Once you inject the service into another service, a virtual proxy with the
same signature of the class representing the service should be injected. The
same happens when calling
The actual class will be instantiated as soon as you try to interact with the service (e.g. call one of its methods).
To check if your proxy works you can check the interface of the received object:
dump(class_implements($service)); // the output should include "ProxyManager\Proxy\LazyLoadingInterface"
If you don't install the ProxyManager bridge and the
ocramius/proxy-manager, the container will just skip over the
flag and instantiate the service as it would normally do.
You can read more about how proxies are instantiated, generated and initialized in the documentation of ProxyManager.