PHP Inversion of Control and Dependency Injection
Let’s look at an example first:
<?php class A { public $b; public $c; public function A() { //TODO } public function Method() { $this->b=new B(); $this->c=new C(); $this->b->Method(); $this->c->Method(); //TODO } } class B { public function B() { //TODO } public function Method() { //TODO echo 'b'; } } class C { public function C() { //TODO } public function Method() { //TODO echo 'c'; } } $a=new A(); $a->Method(); ?>
The above code, we can easily understand one sentence:
A classDepend on Class B and Class C
In other words, if in the future development process, Class B or Class C needs to be modified, once thefunction is renamed, the function If the number of parameters changes, or even if the entire class structure is adjusted, we must also make corresponding adjustments to Class A. The independence of Class A is lost, which is very inconvenient during the development process, which is what we call "One thing affects the whole body." If the two categories are written by two people separately, conflicts often arise at this time. . .
If we really need to change categories B and C, is there any way to not change the code of category A or to change it as little as possible? Inversion of control is used here.High-level modules should not depend on low-level modules, both should rely on abstractions.Inversion of Control (IOC) is an idea,
Dependency Injection (DI) is a method to implement this idea.
The first method is called: constructor injection (this method is not recommended, but it is better than not using it)class A { public $b; public $c; public function A($b,$c) { $this->b=$b; $this->c=$c; } public function Method() { $this->b->Method(); $this->c->Method(); } }
$a=new A(new B(),new C()); $a->Method();
class B { public function B() { //TODO } public function Method() { //TODO echo 'b'; } } class B1 extends B { public function B1() { //TODO } public function Method() { echo 'b1'; } } class B2 extends B { public function B2() { //TODO } public function Method() { echo 'b2'; } }
$a=new A(new B2(),new C()); $a->Method();
Factory modeInjection (recommended)
class Factory { public function Factory() { //TODO } public function create($s) { switch($s) { case 'B': { return new B(); break; } case 'C': { return new C(); break; } default: { return null; break; } } } }
class A { public $b; public $c; public function A() { //TODO } public function Method() { $f=new Factory(); $this->b=$f->create('B'); $this->c=$f->create('C'); $this->b->Method(); $this->c->Method(); //TODO } }
constructor of classes B and C changes, such as modifying function parameters, etc., we Just change the Factory class.
Abstraction should not depend on details, details should depend on abstraction.Abstract the methods in classes B and C and make an
interface IMethod { public function Method(); }
variables and $c variables in the class are no longer a specific variable, but an abstract class type variable. Until the moment of running, their identity is unknown. How is the Method method implemented?
class B implements IMethod { public function B() { //TODO } public function Method() { //TODO echo 'b'; } } class C implements IMethod { public function C() { //TODO } public function Method() { //TODO echo 'c'; } }
Summary Several points:
1. We move the creation of class B objects and class C objects in class A Out of Class A2. Originally Class A relied on Class B and Class C, but now A depends on Factory, and Factory depends on B and C.The above is the detailed content of PHP Inversion of Control and Dependency Injection. 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

AI Hentai Generator
Generate AI Hentai for free.

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

This article will take you through dependency injection, introduce the problems that dependency injection solves and its native writing method, and talk about Angular's dependency injection framework. I hope it will be helpful to you!

Introduction to the method of using dependency injection (DependencyInjection) in the Phalcon framework: In modern software development, dependency injection (DependencyInjection) is a common design pattern aimed at improving the maintainability and testability of the code. As a fast and low-cost PHP framework, the Phalcon framework also supports the use of dependency injection to manage and organize application dependencies. This article will introduce you how to use the Phalcon framework

For testing dependency injection using JUnit, the summary is as follows: Use mock objects to create dependencies: @Mock annotation can create mock objects of dependencies. Set test data: The @Before method runs before each test method and is used to set test data. Configure mock behavior: The Mockito.when() method configures the expected behavior of the mock object. Verify results: assertEquals() asserts to check whether the actual results match the expected values. Practical application: You can use a dependency injection framework (such as Spring Framework) to inject dependencies, and verify the correctness of the injection and the normal operation of the code through JUnit unit testing.

In Go, the dependency injection (DI) mode is implemented through function parameter passing, including value passing and pointer passing. In the DI pattern, dependencies are usually passed as pointers to improve decoupling, reduce lock contention, and support testability. By using pointers, the function is decoupled from the concrete implementation because it only depends on the interface type. Pointer passing also reduces the overhead of passing large objects, thereby reducing lock contention. Additionally, DI pattern makes it easy to write unit tests for functions using DI pattern since dependencies can be easily mocked.

Inversion of Control (IoC) is a software design pattern that separates object dependencies into hard-coded couplings. In Go, IoC can be achieved through interfaces and dependency injection (DI): Interface: Defines the set of methods that types following the interface must implement. Dependency injection: External configuration or code generation sets object dependencies. Tips include: Constructor injection: Specifying dependencies in the constructor. Field injection: Use reflection or code generation to inject dependencies into fields. Interface injection: Passing interface types as parameters to functions or methods.

Answer: Dependency injection and service containers in PHP help to flexibly manage dependencies and improve code testability. Dependency injection: Pass dependencies through the container to avoid direct creation within the function, improving flexibility. Service container: stores dependency instances for easy access in the program, further enhancing loose coupling. Practical case: The sample application demonstrates the practical application of dependency injection and service containers, injecting dependencies into the controller, reflecting the advantages of loose coupling.

Using dependency injection (DI) in Golang unit testing can isolate the code to be tested, simplifying test setup and maintenance. Popular DI libraries include wire and go-inject, which can generate dependency stubs or mocks for testing. The steps of DI testing include setting dependencies, setting up test cases and asserting results. An example of using DI to test an HTTP request handling function shows how easy it is to isolate and test code without actual dependencies or communication.

Inversion of control in the Go language provides flexibility for object-oriented programming by separating object creation and dependency injection: IoC basic principle: external containers or frameworks manage object creation and injection, and objects no longer directly instantiate other objects. Dependency injection: Dependencies are passed to objects as parameters, making the object independent of its dependencies for easy testing and reuse. IoC container: used to manage object creation and injection. The Go language has many ready-made containers to choose from, such as wire and go-wire. Advantages: Enhance testability, improve maintainability, provide flexibility, loosely couple dependencies between objects.
