


Building a PSR-Compatible Dependency Injection Container with PHP Lazy Objects
Exploring Dependency Injection with Lazy Objects in PHP 8.4
In the realm of modern PHP, the release of version 8.4 introduced a groundbreaking feature: Lazy Objects. These objects enable a new way to defer initialization until absolutely necessary, boosting performance and reducing resource usage. This functionality is deeply integrated into the language through enhancements to the ReflectionClass API, as outlined in the Lazy Initialization for Lazy Objects RFC.
Example from the RFC
To illustrate the potential of Lazy Objects, consider the following example directly the RFC:
class MyClass { public function __construct(private int $foo) { // Heavy initialization logic here. } // ... } $initializer = static function (MyClass $ghost): void { $ghost->__construct(123); }; $reflector = new ReflectionClass(MyClass::class); $object = $reflector->newLazyGhost($initializer); // At this point, $object is a lazy ghost object.
This mechanism allows developers to finely control the initialization process, ensuring that resources are only loaded when accessed.
Inspired by this RFC, I set out to build a PSR-11 compatible Dependency Injection Container, leveraging the Lazy Objects API for optimal performance.
The Foundation of the ContainerLazyObject
The core of our container lies in the ContainerLazyObject class. With it, you can register dependencies and initialize them lazily, meaning they are only instantiated when actually needed. Here is the main method that performs this task:
public function set(string $id, object|string $concrete): void { $reflector = new ReflectionClass($id); $initializer = $concrete; if (is_string($concrete)) { $initializer = function(object $instance) use ($concrete): void { $this->instances[$instance::class] = $concrete($this); }; } if (is_object($concrete) && !$concrete instanceof Closure) { $initializer = function(object $instance) use ($concrete): void { $this->instances[$instance::class] = $concrete; }; } $this->instances[$id] = $reflector->newLazyGhost($initializer); }
Registering Services in the Container
Our container supports various ways of registering services, offering flexibility to developers. Here are some examples:
$container = new ContainerLazyObject(); $containerer->set(DatabaseService::class, fn() => new DatabaseService(new LoggerService())); $container->set(LoggerService::class, fn() => new LoggerService()); // Alternative approach with class names $container->set(DatabaseService::class, DatabaseService::class); $containerr->set(LoggerService::class, LoggerService::class); // Using already instantiated objects $container->set(DatabaseService::class, new DatabaseService(new LoggerService())); $container->set(LoggerService::class, new LoggerService());
This flexibility makes the ContainerLazyObject adaptable to various scenarios, whether dynamically building dependencies or reusing pre-configured objects.
Retrieving Services from the Container
Once services are registered in the container, you can retrieve them whenever needed. The container ensures that services are lazily instantiated, so they won’t be created until actually requested. Here is an example of how to retrieve the registered services:
// Retrieving the services from the container $loggerService = $container->get(LoggerService::class); $databaseService = $container->get(DatabaseService::class);
The Core of ContainerLazyObject The heart of our container lies in the ContainerLazyObject class. With it, you can register dependencies and initialize them lazily, meaning they are only created when they are actually used. Here is the main method that performs this task:
public function set(string $id, object|string $concrete): void { $reflector = new ReflectionClass($id); $initializer = $concrete; if (is_string($concrete)) { $initializer = function(object $instance) use ($concrete): void { $this->instances[$instance::class] = $concrete($this); }; } if (is_object($concrete) && !$concrete instanceof Closure) { $initializer = function(object $instance) use ($concrete): void { $this->instances[$instance::class] = $concrete; }; } $this->instances[$id] = $reflector->newLazyGhost($initializer); }
PSR-11 Compatibility
An additional advantage of the ContainerLazyObject is its compatibility with PSR-11, the PHP standard for dependency injection containers. This ensures interoperability with libraries and frameworks following the specification, making it a lightweight and universal solution.
Performance Comparison with Other Containers
To measure the performance of our container, I used PhpBench in a controlled environment, comparing it to popular alternatives: Pimple, Illuminate, and PHP-DI. The results were encouraging:
class MyClass { public function __construct(private int $foo) { // Heavy initialization logic here. } // ... } $initializer = static function (MyClass $ghost): void { $ghost->__construct(123); }; $reflector = new ReflectionClass(MyClass::class); $object = $reflector->newLazyGhost($initializer); // At this point, $object is a lazy ghost object.
Our container demonstrated excellent performance, being significantly faster than more robust alternatives like Illuminate Container and PHP-DI in simple dependency resolution scenarios.
The Complete Class
public function set(string $id, object|string $concrete): void { $reflector = new ReflectionClass($id); $initializer = $concrete; if (is_string($concrete)) { $initializer = function(object $instance) use ($concrete): void { $this->instances[$instance::class] = $concrete($this); }; } if (is_object($concrete) && !$concrete instanceof Closure) { $initializer = function(object $instance) use ($concrete): void { $this->instances[$instance::class] = $concrete; }; } $this->instances[$id] = $reflector->newLazyGhost($initializer); }
Conclusion
PHP 8.4 and its Lazy Objects have opened new possibilities to simplify and optimize dependency injection. Our ContainerLazyObject, in addition to being lightweight, efficient, and flexible, is PSR-11 compliant, ensuring interoperability with other libraries and frameworks.
Try this approach and see how it can simplify dependency management in your next project!
The above is the detailed content of Building a PSR-Compatible Dependency Injection Container with PHP Lazy Objects. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Alipay PHP...

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

Sending JSON data using PHP's cURL library In PHP development, it is often necessary to interact with external APIs. One of the common ways is to use cURL library to send POST�...
