Laravel like facades por PSR11 containers

v2.0.0 2020-08-12 03:14 UTC

This package is auto-updated.

Last update: 2020-11-12 04:10:32 UTC


Build Status

Laravel like Facades (static proxies) for PSR11 containers.

class HomeController
    public function __invoke()
        // It just works!
        return View::render('home.index', [
            'articles' => DB::query('SELECT * FROM articles')


I will show you a simple Slim application.

Your application bootstrap:


use App\Controllers\HomeController;
use App\Facades\DB;
use App\Facades\View;
use ReStatic\ProxyManager;
use Slim\Factory\AppFactory;
use Twig\Environment as TwigEnvironment;
use Twig\Loader\FilesystemLoader as TwigFilesystemLoader;

require __DIR__ . '/../vendor/autoload.php';

// Setup Container
$container = new \DI\Container();
$container->set('db', function () {
    return new PDO('mysql:dbname=testdb;host=', 'dbuser', 'dbpass');
$cointainer->set('view', function () {
    $loader = new TwigFilesystemLoader('/path/to/templates');
    return new TwigEnvironment($loader);

// Setup Facades
$proxyManager = new ProxyManager($container);
$proxyManager->addProxy('DB', DB::class);
$proxyManager->addProxy('View', View::class);

// Create App
$app = AppFactory::create();

$app->get('/', HomeController::class);


Your Static Proxy classes:

// app/Facades/View.php
class View extends StaticProxy
    public static function getInstanceIdentifier()
        return 'view';

// app/Facades/DB.php
class DB extends StaticProxy
    public static function getInstanceIdentifier()
        return 'db';

Your controller class:


namespace App\Controllers;

class HomeController
    public function __invoke()
        return View::render('home.index', [
            'articles' => DB::query('SELECT * FROM articles')

Pretty cool, huh? Some interesting things to note about this example is that we've actually hidden the fact that we are using PDO and Twig from the controller. We could easily swap something else in that uses the same interfaces, and the controller code would not need to be altered. All we would need to do is put different objects into the application container. In fact, that is exactly how testing the controller would work. The test could be bootstrapped with mock or stub objects put into the container.

Static interfaces without the static pitfalls.


Facades? Static Proxies? Isn't using static methods considered a bad practice?

Using static methods and classes makes your code harder to test. This is because your code becomes tightly coupled to the class being referenced statically, and mocking static methods for unit tests is difficult. For this and other reasons, using static methods is generally discouraged by object-oriented programming (OOP) experts. Generally, techniques involving design patterns like Service Locator and Dependency Injection (DI) are preferred for managing object dependencies and composition.

But... using static methods is really easy.

True, and PHP developers that prefer frameworks like CodeIgniter, Laravel, Kohana, and FuelPHP are very accustomed to using static methods in their application development. In some cases, it is an encouraged practice among these communities, who argue that it makes the code more readable and contributes to Rapid Application Development (RAD).

So, is there any kind of compromise?

Yep! Laravel 4 has a concept called "facades" (Note: This is not the same as the Facade design pattern). These act as a static interface, or proxy, to an actual object instance stored in a service container. The static proxy is linked to the container using a few tricks, including defining class aliases via PHP's class_alias() function, and the use of the magic __callStatic() method. We can thank Taylor Otwell for developing this technique.

OK, then what is the point of ReStatic?

ReStatic uses the same technique as Laravel's "facades" system, but provides two additional, but important, features:

  1. It works with any framework's service container - ReStatic relies on the ContainerInterface of the PSR-11 standard. You can use the Acclimate library to adapt any third-party containers to the normalized container interface that ReStatic depends on.
  2. It works within any namespace - ReStatic injects an autoloader onto the stack, so no matter what namespace or scope you try to reference your aliased static proxy from, it will pass through the ReStatic autoloader. You can configure ReStatic to create the aliases in the global namespace, the current namespace, or a specific namespace.

ReStatic Concepts

  • Static Proxy – Static class that proxies static method calls to instance methods on its Proxy Subject.
  • Proxy Subject (Instance) – An object instance, stored in a Container, that is linked to a Static Proxy.
  • Proxy Manager – Mediating object used to associate Static Proxies to an Alias Loader and Container.
  • Alias – A memorable class name used as an alias to a fully-qualified class name of a Static Proxy class.
  • Alias Loader – Maintainer of the associations between Aliases and Static Proxies. It is injected into the autoloader stack to handle Aliases as they are referenced.
  • Container – A IoC container (e.g., a Service Locator or DIC) that provides the Proxy Subject instances. It must implement the PSR-11 stardard's ContainerInterface.
  • Instance Identifier – An identifier used to fetch a Proxy Subject from a Container. Each Static Proxy must specify the Instance Identifier needed to get its Proxy Subject.
  • Root Namespace – The namespace that an Alias can be referenced in. This can be configured as the global namespace (default), a specific namespace, or any namespace (i.e., the Alias works from any namespace).


ReStatic is based on the awesome package XStatic created by Jeremy Lindblom.


I would not consider myself to be for or against the use of static proxy interfaces (or Laravel's "Facades"), but I do think it is a fascinating and unique idea, and that it is very cool that you can write code this way and still have it work and be testable. I am curious to see if developers, especially library and framework developers, find ways to use, but not require, these static proxy interfaces in order to make their projects appeal to a wider range of PHP developers.