How is the facade pattern in Laravel implemented, which appears as static calls but works as regular objects?

Facades in Laravel appear as static calls, but they actually work through PHP's mechanism — the magic method __callStatic() and Laravel's service container.

Here's how it works:

• A facade is a class that extends the base Facade class.
• Inside the facade, there's a method getFacadeAccessor() that returns the service key from the container.
• When a static method of the facade is called, PHP redirects the call to __callStatic(), which internally retrieves an instance of the object from the service container using the key.
• Then, the method call is delegated to this instance, just like a regular object.

Thus, facades provide a convenient syntax for static calls, hiding the dynamic resolution of dependencies and object handling behind the scenes.

Example:

class Cache extends Facade {
    protected static function getFacadeAccessor() {
        return 'cache';
    }
}

// Call
Cache::get('key'); // actually calls the get() method of the cache object from the container