New features and changes in Laravel 8 queue system

The following is the tutorial column of Laravel to introduce you to the new features and changes of the Laravel 8 queue system. I hope it will be helpful to friends in need!

                                               

Laravel 8 comes with cool new features and some changes to the queue system. In this article, we'll look at these features and changes.

Change

---

Backoff

has beenretryAfter() Methods and properties of retryAfter queued jobs, emails, notifications and listeners were renamed to backoff. The

php artisan queue:work command's --delay option has also been renamed to --backoff.

You should also know that you can now pass an array to the backoff property to instruct the worker to implement exponential backoff:

public $backoff = [30, 60];

or from The backoff() method returns an array:

public function backoff()
{
    return [30, 60]; 
}

Using exponential backoff here, we instruct the worker to delay 30 seconds after the first failure to retry the job, and then delay 60 seconds after each failure .

You can also use exponential backoff on the queue:work command:

php artisan queue:Work --backoff=30,60

Job Expiration

Queue the job, The timeoutAt property for notifications and listeners has been renamed to retryUntil.

Use $retryUntil to instruct the worker to continue retrying the job until some time in the future.

You can add retryUntil as a public property of the job class or as a retryUntil method:

public function retryUntil()
{
    return now()->addDay();
}

New Features

Queue Closure

You can now chain calls to the catch() method when dispatching a queue closure:

dispatch(function () {
    // Job logic...
})->catch(function (Throwable $e) {
    // Handle Failure...
});

if If the job fails, the closure provided to the catch() method will be called.

Database Driver Reliability

Laravel will now perform operations within a transaction when a job is released back to the queue using the database queue driver. This means that jobs will not be removed from the queue unless a new published instance is added. This greatly reduces the chance of job failure.

Redis Driver Efficiency

When using the Redis queue driver to batch distribute a set of jobs, Laravel will perform the operation by sending a single command to Redis. Previously, Laravel used to send multiple rpush commands to Redis, one for each job.

Worker Graceful Termination

Starting with Laravel 8, Workers will exit gracefully and call any termination registered by App::Terminating() callback.

Worker self-terminating

To avoid memory leaks, it is common practice to kill your workers from time to time and then let your process monitoring tool start a new worker. This is usually done by adding a CRON job that runs the queue:restart command.

In Laravel 8, you can instruct Workers to exit after processing a certain number of jobs or running for a specific number of seconds:

php artisan queue:work --max-jobs=1000 --max-time=3600

Named Workers

You now add the --name option to the queue:work command:

php artisan queue:work --name=notifications

The main purpose of adding this functionality is to allow people to customize Workers at runtime How to choose which queue to process a task:

Worker::popUsing('notifications', function ($pop) {
    $queues = time()->atNight() 
        ? ['mail', 'webhooks'] 
        : ['push-notifications', 'sms', 'mail', 'webhooks'];

    foreach ($queues as $queue) {
        if (! is_null($job = $pop($queue))) {
            return $job;
        }
    }
});

Task Batching

Laravel's task batching allows you to dispatch many tasks for parallel processing by your Workers. You can perform actions after all tasks in the batch have been processed or any batch task has failed:

Bus::batch([
    new ProcessFile(1),
    new ProcessFile(2),
    new ProcessFile(3),
])->dispatch();

You can find more information about "Job Batching" in Official Documentation More information.

Job Chain

You can now schedule a series of jobs directly using Bus:

Bus::chain([
    new ExtractReports,
    new GenerateReport,
    new SendResults,
])->dispatch();

You can also add a catch() Callback that will be called if any job in the chain fails:

Bus::chain([
    new ExtractReports,
    new GenerateReport,
    new SendResults,
])->catch(function(){
    // Handle the chain failure.
})
->dispatch();

Horizon Balance Rate

Two new ones have been added to Horizon Configuration options: balanceMaxShift and balanceCooldown.

 'environments' => [
    'environment' => [
        'supervisor-1' => [
            'balanceMaxShift' => 5,
        ],
    ],
],

balanceMaxShift Sets the maximum number of worker processes to add or remove each time Horizon expands the worker pool. In previous versions of Horizon, only one worker process was added or removed, now you can control that number.

As for balanceCooldown, it sets the number of seconds to wait between each scaling operation. In earlier versions of Horizon, this was hardcoded to 3 seconds.

 'environments' => [
    'environment' => [
        'supervisor-1' => [
            'balanceCooldown' => 1,
        ],
    ],
],

原文地址：https://dev.to/themsaid/features-and-changes-coming-to-laravel-8-s-queue-system-5amg

译文地址：https://learnku.com/laravel/t/50086

The above is the detailed content of New features and changes in Laravel 8 queue system. For more information, please follow other related articles on the PHP Chinese website!