摘要：配有內(nèi)置的隊列系統(tǒng)，可幫助您在后臺運(yùn)行任務(wù)，并通過簡單的來配置系統(tǒng)在不同情況下起作用。您可以在中管理隊列配置，默認(rèn)情況下它有使用不同隊列驅(qū)動的幾個連接，您可以看到項目中可以有多個隊列連接，也可以使用多個隊列驅(qū)動程序。

原文鏈接https://divinglaravel.com/queue-system/before-the-dive

Laravel receives a request, does some work, and then returns a response to the user, this is the normal synchronous workflow of a web server handling a request, but sometimes you need to do some work behind the scenes that doesn"t interrupt or slowdown this flow, say for example sending an invoice email to the user after making an order, you don"t want the user to wait until the mail server receives the request, builds the email message, and then dispatches it to the user, instead you"d want to show a "Thank You!" screen to the user so that he can continue with his life while the email is being prepared and sent in the background.

Laravel接收請求，做一些工作，然后向用戶返回響應(yīng)，這是處理請求的Web服務(wù)器的正常同步工作流程，但有時您需要在后臺執(zhí)行不中斷或減慢的一些流程，例如在訂單之后向用戶發(fā)送發(fā)票電子郵件，你不想讓用戶等待郵件服務(wù)器接收請求,構(gòu)建電子郵件消息,然后分派給用戶，你只要向屏幕發(fā)送“謝謝!”給用戶,電子郵件在后臺準(zhǔn)備和發(fā)送，他繼續(xù)做他自己的事。

Laravel is shipped with a built-in queue system that helps you run tasks in the background & configure how the system should react in different situation using a very simple API.

Laravel配有內(nèi)置的隊列系統(tǒng)，可幫助您在后臺運(yùn)行任務(wù)，并通過簡單的API來配置系統(tǒng)在不同情況下起作用。

You can manage your queue configurations in config/queue.php, by default it has a few connections that use different queue drivers, as you can see you can have several queue connections in your project and use multiple queue drivers too.

您可以在 config/queue.php中管理隊列配置，默認(rèn)情況下它有使用不同隊列驅(qū)動的幾個連接，您可以看到項目中可以有多個隊列連接，也可以使用多個隊列驅(qū)動程序。

We"ll be looking into the different configurations down the road, but let"s first take a look at the API:

我們將研究不同的配置，但請先看看API：

Queue::push(new SendInvoice($order));

return redirect("thank-you");

The Queue facade here proxies to the queue container alias, if we take a look at QueueQueueServiceProvider we can see how this alias is registered:

隊列Queue facade 是 queue 容器別名，如果我們看看QueueQueueServiceProvider ，我們可以看到這個別名是如何注冊的：

protected function registerManager()
{
    $this->app->singleton("queue", function ($app) {
        return tap(new QueueManager($app), function ($manager) {
            $this->registerConnectors($manager);
        });
    });
}

So the Queue facade proxies to the QueueQueueManager class that"s registered as a singleton in the container, we also register the connectors to different queue drivers that Laravel supports using registerConnectors():

所以 Queue facade 代理到在容器中注冊為 QueueQueueManager 類的單例，我們還將連接器注冊到Laravel所支持使用的registerConnectors()的不同隊列驅(qū)動程序中：

public function registerConnectors($manager)
{
    foreach (["Null", "Sync", "Database", "Redis", "Beanstalkd", "Sqs"] as $connector) {
        $this->{"register{$connector}Connector"}($manager);
    }
}

This method simply calls the register{DriverName}Connector method, for example it registers a Redis connector:

該方法只需調(diào)用注冊 register{DriverName}Connector方法，例如注冊一個Redis連接器：

protected function registerRedisConnector($manager)
{
    $manager->addConnector("redis", function () {
        return new RedisConnector($this->app["redis"]);
    });
}

The addConnector() method stores the values to a QueueManager::$connectors class property.

A connector is just a class that contains a connect() method which creates an instance of the desired driver on demand, here"s how the method looks like inside QueueConnectorsRedisConnector:

addConnector() 方法將值存儲到 QueueManager::$connectors 類屬性。
連接器只是一個類，它包含一個 connect() 方法，它根據(jù)需要創(chuàng)建所需驅(qū)動的一個實例，方法看起來像在QueueConnectorsRedisConnector里面:

public function connect(array $config)
{
    return new RedisQueue(
        $this->redis, $config["queue"],
        Arr::get($config, "connection", $this->connection),
        Arr::get($config, "retry_after", 60)
    );
}

So now The QueueManager is registered into the container and it knows how to connect to the different built-in queue drivers, if we look at that class we"ll find a __call() magic method at the end:

所以現(xiàn)在QueueManager被注冊到容器中，它知道如何連接到不同的內(nèi)置隊列驅(qū)動，如果我們看下這個類，我們將在最后找到一個__call() 魔術(shù)方法：

public function __call($method, $parameters)
{
    return $this->connection()->$method(...$parameters);
}

All calls to methods that don"t exist in the QueueManager class will be sent to the loaded driver, for example when we called the Queue::push() method, what happened is that the manager selected the desired queue driver, connected to it, and called the push method on that driver.

對 QueueManager 類中不存在的方法的所有調(diào)用將被發(fā)送到加載的驅(qū)動中，例如當(dāng)我們調(diào)用 Queue::push() 方法時，所發(fā)生的是manager選擇了連接到它的所需隊列驅(qū)動 ，并在該驅(qū)動上調(diào)用 push 方法。

Let"s take a look at the connection() method:

讓我們看下 connection() 方法

public function connection($name = null)
{
    $name = $name ?: $this->getDefaultDriver();

    if (! isset($this->connections[$name])) {
        $this->connections[$name] = $this->resolve($name);

        $this->connections[$name]->setContainer($this->app);
    }

    return $this->connections[$name];
}

When no connection name specified, Laravel will use the default queue connection as per the config files, the getDefaultDriver() returns the value of config/queue.php["default"]:

當(dāng)沒有指定連接名稱時，Laravel將根據(jù)配置文件使用默認(rèn)隊列連接， getDefaultDriver() 返回config/queue.php["default"]的值：

public function getDefaultDriver()
{
    return $this->app["config"]["queue.default"];
}

Once a driver name is defined the manager will check if that driver was loaded before, only if it wasn"t it starts to connect to that driver and load it using the resolve() method:

一旦定義了驅(qū)動名稱，管理器將檢查該驅(qū)動是否已被加載，只有當(dāng)它不是開始連接到該驅(qū)動程序并使用 resolve() 方法加載它時：

protected function resolve($name)
{
    $config = $this->getConfig($name);

    return $this->getConnector($config["driver"])
                ->connect($config)
                ->setConnectionName($name);
}

First it loads the configuration of the selected connection from your config/queue.php file, then it locates the connector to the selected driver, calls the connect() method on it, and finally sets the connection name for further use.

首先從 config/queue.php 文件加載所選連接的配置，然后將連接器定位到所選驅(qū)動，調(diào)用 connect() 方法，最后設(shè)置連接名稱以供進(jìn)一步使用。

Yes, when you do Queue::push() you"re actually calling the push method on the queue driver you"re using, each driver handles the different operations in its own way but Laravel provides you a unified interface that you can use to give the queue manager instructions despite of what driver you use.

是的，當(dāng)您執(zhí)行 Queue::push() 時，您正在使用的隊列驅(qū)動中調(diào)用 push 方法，每個驅(qū)動以其自己的方式處理不同的操作，但Laravel為您提供了一個統(tǒng)一的接口，您可以使用它告訴隊列管理器你使用了什么驅(qū)動程序。

Easy, you can call Queue::addConnector() with the name of your custom driver as well as a closure that explains how a connection to that driver could be acquired, also make sure that your connector implements the QueueConnectorsConnectorInterface interface.

簡單來說，您可以使用自定義驅(qū)動的名稱調(diào)用 Queue::addConnector() ，以及一個解釋如何獲取與該驅(qū)動程序的連接的閉包，還要確保您的連接器實現(xiàn) QueueConnectorsConnectorInterface 接口。

Once you register the connector, you can use any connection that uses this driver:

注冊連接器后，您可以使用任何使用此驅(qū)動的連接：

Queue::connection("my-connection")->push(...);

Continue to "Preparing Jobs For Queue"

繼續(xù)“準(zhǔn)備隊列作業(yè)”

轉(zhuǎn)載請注明：?轉(zhuǎn)載自Ryan是菜鳥 | LNMP技術(shù)棧筆記

如果覺得本篇文章對您十分有益，何不 打賞一下

本文鏈接地址:?剖析Laravel隊列系統(tǒng)之初探