Laravel单例模式如何在后续调用中体现实例修改的变化？

Great question—this trips up a lot of folks at first, but it boils down to how PHP handles objects and how Laravel's container stores singletons. Let me break it down simply:

1. Laravel's Singleton Stores a Reference to the Object, Not a Copy #

When you bind a singleton to the Laravel container, here's what happens under the hood:

• The first time you resolve the class (like app(MySingleton::class)), the container creates a new instance of the object.
• Instead of creating a fresh copy every time after that, the container saves a reference to this single object in its $instances property.
• Every subsequent call to resolve the singleton just returns that same reference.

2. PHP Objects Are Passed by Reference #

In PHP, when you assign an object to a variable (or pass it around), you're not copying the entire object—you're passing a reference to the original object in memory. Think of it like having multiple nicknames for the same person: if you change the person's hair color using one nickname, everyone using any other nickname will see the new hair color too.

Example to Illustrate #

Let's say you have a simple singleton class:

class MySingleton {
    public $value = "Original Value";
}

Bind it as a singleton:

app()->singleton(MySingleton::class);

Now modify it in your controller:

// Get the singleton instance
$controllerInstance = app(MySingleton::class);
// Modify its state
$controllerInstance->value = "Updated Value";

Then access it in another function or class:

$otherInstance = app(MySingleton::class);
echo $otherInstance->value; // Outputs "Updated Value"

This works because $controllerInstance and $otherInstance are both pointing to the exact same object in memory. There's only one instance ever created, so any changes to it are global across all places that reference it.

3. How This Differs From Non-Singleton Bindings #

If you used a regular binding (not a singleton) like app()->bind(MyClass::class), every call to app(MyClass::class) would create a brand new object. Modifying one instance wouldn't affect others because they're separate objects in memory.

Key Takeaway #

Laravel's singleton pattern ensures there's only one instance of your class alive in the application's lifecycle. Since all calls to resolve the singleton return a reference to that single instance, any modifications you make to it will be reflected everywhere else that uses the singleton.

内容的提问来源于stack exchange，提问作者fayis003