[I switched this website from Symfony to Laravel](/blog/why-I-migrated-this-website-from-symfony-to-laravel) 2,5 years ago, and I [love Laravel Container](/blog/what-i-prefer-about-laravel-dependency-injection-over-symfony) ever since.

Symfony and Laravel containers are very similar - read this [compare post](/blog/experiment-how-i-replaced-symfony-di-with-laravel-container-in-ecs) if you know one and want to understand the other.

Yet, I **always patch Laravel Container in `/vendor`** for all projects I use.

Single line change.

Why and where?

Tomas Votruba

The post discusses patching the Laravel Container to optimize performance by ensuring services are treated as singletons rather than being instantiated multiple times. The suggested approach avoids extensive configuration by modifying a single line of code in the Laravel container file. The article highlights the benefits of using patches stored in an open-source repository to simplify the process across projects.

The Patch for Laravel Container

Default Behavior for Unregistered Service

<p>My issue here is what if you need something to not be a singleton and be able to get multiple instance?</p>
<p>If I understood it right, this forces everything to be a Singleton all the time</p>
