Service container and dependency injection analysis in PHP

不言
Release: 2023-04-02 16:46:02
Original
3305 people have browsed it

This article mainly introduces the service container and dependency injection in PHP, which has certain reference value. Now I share it with you. Friends in need can refer to it

Dependency Injection

When class A needs to depend on class B, that is to say, when an object of class B needs to be instantiated in class A for use, if the functions in class B change, it will also cause the use of class B in class A to also Following the modification, class A and class B are highly coupled. The solution at this time is that class A should rely on the interface of class B and hand over the instantiation of specific classes to the outside.

Take the notification module commonly used in our business.

<?php

/**
 * 定义了一个消息类
 * Class Message 
 */
class  Message{

  public function seed()
  {
      return &#39;seed email&#39;;

  }
}
/*
 * 订单产生的时候 需要发送消息
 */
class Order{

    protected $messager = &#39;&#39;;

    function __construct()
    {
        $this->messager = new Message();

    }

    public function seed_msg()
    {

        return $this->messager->seed();

    }
}
$Order = new Order();
$Order->seed_msg();
Copy after login

The above code is our traditional writing method. First, the class sent by the message. Then where we need to send a message, call the interface for sending the message. One day you need to add an interface for sending text messages to meet different needs. Then you will find that you need to make changes in the Message class. You also need to make changes in the Order class. This seems very troublesome. At this time, the idea of ​​dependency injection came into being. Let’s make an adjustment to the code

<?php

/**
 * 为了约束我们先定义一个消息接口
 * Interface Message
 */
interface  Message{

  public function seed();
}

/**
 * 有一个发送邮件的类
 * Class SeedEmail
 */
class SeedEmail implements Message
{

    public function seed()
    {

        return  &#39;seed email&#39;;

        // TODO: Implement seed() method.
    }

}

/** 
 *新增一个发送短信的类
 * Class SeedSMS
 */
class SeedSMS implements Message
{
    public function seed()
    {
        return &#39;seed sms&#39;;
        // TODO: Implement seed() method.
    }


}
/*
 * 订单产生的时候 需要发送消息
 */
class Order{

    protected $messager = &#39;&#39;;

    function __construct(Message $message)
    {
        $this->messager = $message;

    }
    public function seed_msg()
    {
        return $this->messager->seed();
    }
}
//我们需要发送邮件的时候
$message = new SeedEmail();
//将邮件发送对象作为参数传递给Order
$Order = new Order($message);
$Order->seed_msg();


//我们需要发送短信的时候
$message = new SeedSMS();
$Order = new Order($message);
$Order->seed_msg();
Copy after login

so that we can realize the idea of ​​dependency injection. Is it very convenient to expand?

Service container

The service container I understand is a factory that automatically generates classes.
<?php
/**
 * 为了约束我们先定义一个消息接口
 * Interface Message
 */
interface  Message{

    public function seed();
}

/**
 * 有一个发送邮件的类
 * Class SeedEmail
 */
class SeedEmail implements Message
{

    public function seed()
    {

        return  &#39;seed email&#39;;

        // TODO: Implement seed() method.
    }

}

/**
 *新增一个发送短信的类
 * Class SeedSMS
 */
class SeedSMS implements Message
{
    public function seed()
    {
        return &#39;seed sms&#39;;
        // TODO: Implement seed() method.
    }

}


/**
 * 这是一个简单的服务容器
 * Class Container
 */
class Container
{
    protected $binds;

    protected $instances;

    public function bind($abstract, $concrete)
    {
        if ($concrete instanceof Closure) {
            $this->binds[$abstract] = $concrete;
        } else {
            $this->instances[$abstract] = $concrete;
        }
    }

    public function make($abstract, $parameters = [])
    {
        if (isset($this->instances[$abstract])) {
            return $this->instances[$abstract];
        }

        array_unshift($parameters, $this);

        return call_user_func_array($this->binds[$abstract], $parameters);
    }
}

//创建一个消息工厂
$message = new  Container();
//将发送短信注册绑定到工厂里面
$message->bind(&#39;SMS&#39;,function (){
     return   new  SeedSMS();
});
//将发送邮件注册绑定到工厂
$message->bind(&#39;EMAIL&#39;,function (){
   return new  SeedEmail();
});
//需要发送短信的时候
$SMS  = $message->make(&#39;SMS&#39;);
$SMS->seed();
Copy after login

container is a simple service container with two methods bind and make
bind It is to bind the service object to the container. make is to take out the object from the container.

bind

In the bind method you need to pass in a concrete We can pass in an instance object or a closure function.
You can see that I am using a closure function. In fact, you can also write it like this

$sms = new  SeedSMS();
$message->bind(&#39;SMS&#39;,$sms);
Copy after login

The difference between this latter writing method and closure is that we need to instantiate the object first before we can proceed easily. Binding services. Closures only instantiate objects when we use this service. It can be seen that closures have many advantages.

make

make method is the method to exit the container. It first determines whether there is a current and existing service object in the instances variable, and returns directly if there is. If not, an object will be returned through call_user_func_array. For the usage of call_user_func_array, you can check the usage of
call_user_func in PHP

The above is the entire content of this article. I hope it will be helpful to everyone's learning. For more related content, please pay attention to the PHP Chinese website !

Related recommendations:

Analysis of the PHP container Pimple running process

Solution to Chinese random coding of gitbash PHP execution output

The above is the detailed content of Service container and dependency injection analysis in PHP. For more information, please follow other related articles on the PHP Chinese website!

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template