Laravel queue service provides a unified API for various background queues. The following article mainly introduces you to the most basic operation tutorial on using Queue in Laravel. The article introduces it in detail through sample code. Friends who need it You can use it as a reference, let’s take a look below.
Preface
The queue service in laravel is no different from other queue services. They are the simplest and most common ones that are most in line with human thinking. The process: There is a place to store queue information, a PHP process writes tasks when running, and another PHP daemon process polls the queue information, executes and deletes tasks that meet the execution requirements. Since PHP is a URL-driven synchronous language and inherently blocking, it is not surprising that Laravel provides a daemon tool to query and execute queue information.
It was the first time I came into contact with Laravel’s queue in the past two days, and it took a long time. . . After all the hard work, I still feel that I don’t know how to use Laravel. The documentation is relatively simple and summarized, and it’s a bit difficult to read the source code (but reading the source code and slowly debugging and verifying it is still the most reliable).
The following is a simple demo of mine, which only uses the most basic operations of the queue. More advanced operations require more time:)
Like me, there are some queues for getting started with Laravel. Students who are in difficulty can communicate with each other.
Configuration
Add Redis package
In composer.json Add "predis/predis": "~1.0" to the require section, and then composer up to update it.
database.php
Configure the redis database part in the database.php configuration file. There is a default connection by default. Just use this: )
According to the configuration items required in this default connection, edit the .env configuration file and fill in the REDIS_HOST, REDIS_PASSWORD, and REDIS_PORT with the corresponding values of Redis in your own server.
queue.php
First you need to configure QUEUE_DRIVER in .env. Because you plan to use Redis now, you configure it to redis.
Then configure the redis connection in the connections section of queue.php, where the value corresponding to connection is the default connection of redis in database.php.
Task class
The next step is to write the actual operation class. Laravel provides the artisan command to simplify the creation of task classes:
php artisan make:job Demo
The Jobs directory will be generated in the app directory, which already has the Demo.php task class.
Lumen does not have this artisan command, but it is very convenient. By default, there will be an ExampleJob.php already written, just copy it and change the name.
First write a simple log output test, in the handle method:
Log::info('Hello, queue');
Issuing tasks
Now write an entry function to push the task to the queue. Use the auxiliary function dispatch():
Use the following method in Laravel:
Demo::dispatch();
Use the following method in Lumen:
dispatch(new Demo);
Open the queue
If everything goes well, this is the last step. Execute in the command line:
php artisan queue:listen --queue=default
It will monitor the queue and output simple execution conditions, such as:
[2017-11-07 02:12:47] Processing: App\Jobs\Demo [2017-11-07 02:12:47] Processed: App\Jobs\Demo
After there are no problems, you can let this queue script execute in the background:
php artisan queue:work --daemon --quiet --queue=default 1>> /dev/null 2>&1
Advanced:)
When pushing to the queue, there is usually a need to pass parameters, so how do you pass them here?
Parameter passing
Passing in
The method of passing parameters in the entry function is as follows:
The following method is used in Laravel:
$param = 'Stephen'; Demo::dispatch($param);
The following method is used in Lumen:
$param = 'Stephen'; dispatch(new Demo($param));
Receive
The method of receiving parameters in the task class is as follows:
protected $param; /** * Create a new job instance. * * @return void */ public function __construct($param) { $this->param = $param; } /** * Execute the job. * * @return void */ public function handle() { Log::info('Hello, ' . $this->param); }
This is the first attempt. There are many advanced usages, such as delayed distribution, error handling, priority, failure handling, etc. I will continue to write in the future:)
Multiple Queues
This is an issue that must be taken into consideration. It is impossible for me to put all tasks in a queue called default, which makes it difficult to manage the queue.
To specify different queues, it is very simple. Just follow the onQueue() method immediately after dispatch():
Demo::dispatch()->onQueue('emails');
No, I don't seem to have defined this queue called emails. Well, naturally we need to make some changes. The redis configuration queue in the queue.php configuration file is changed from default to {default}. The effect of this is that the name of the queue can be obtained dynamically from runtime instead of being hard-coded. .
If you use the Lumen framework, you will get an error if you write directly like this: Call to a member function onQueue() on string.
原因在于 Lumen 的 Job 基类中并没有使用 Illuminate\Foundation\Bus\Dispatchable 这个 trait,而是直接使用 Illuminate\Bus\Queueable 中的 onQueue() 方法。
那么现在就很清楚了,我们的 Job 类使用了 Illuminate\Bus\Queueable 这个 trait,所以需要在 Job 类上调用这个 onQueue() 方法。
$job = new XXXJob(); dispatch($job->onQueue('queue-name'));
当我们在开启队列的时候:
php artisan queue:work --queue=emails
这里指定的队列名 emails 和 dispatch 时指定的队列名保持一致即可。
总结
The above is the detailed content of Tutorial on the most basic operation of using Queue in Laravel. For more information, please follow other related articles on the PHP Chinese website!