Lazy Services

Edit this page

Warning: You are browsing the documentation for Symfony 2.3, which is no longer maintained.

Read the updated version of this page for Symfony 6.1 (the current stable version).

Lazy Services


Lazy services were introduced in Symfony 2.3.

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 a NewsletterManager and you inject a mailer service into it. Only a few methods on your NewsletterManager actually use the mailer, but even when you don't need it, a mailer service is always instantiated in order to construct your NewsletterManager.

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.


In order to use the lazy service instantiation, you will first need to install the ProxyManager bridge:

$ composer require symfony/proxy-manager-bridge:~2.3


If you're using the full-stack framework, the proxy manager bridge is already included but the actual proxy manager needs to be included. So, run:

$ composer require ocramius/proxy-manager:~1.0

Afterwards compile your container and check to make sure that you get a proxy for your lazy services.


You can mark the service as lazy by manipulating its definition:

  • YAML
  • XML
  • PHP
     class: Acme\Foo
     lazy: true

You can then require the service from the container:

$service = $container->get('foo');

At this point the retrieved $service should be a virtual proxy with the same signature of the class representing the service. You can also inject the service just like normal into other services. The object that's actually injected will be the proxy.

To check if your proxy works you can simply check the interface of the received object.


If the class implements the ProxyManager\Proxy\LazyLoadingInterface your lazy loaded services are working.


If you don't install the ProxyManager bridge and the ocramius/proxy-manager, the container will just skip over the lazy flag and simply instantiate the service as it would normally do.

The proxy gets initialized and the actual service is instantiated as soon as you interact in any way with this object.

Additional Resources

You can read more about how proxies are instantiated, generated and initialized in the documentation of ProxyManager.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.