By: Pankaj Sakariya

May 16, 2019

Laravel 5.8.14 Holds New Job-based Retry Delay And More

The ultra-fast and the most popular PHP framework, Laravel is a versatile framework and is also famous for releasing periodic updates every six months. Laravel framework gathered 51940 stars on GitHub.

The figures give you an idea about the popularity across different verticals of the industry.

The combination of PHP along with Laravel development services is a power-pact combo with some of great features, easy documentation, and a huge community.

With the World moving towards modernization, web application development should also adopt a modern path.

The team behind the framework has to think out of the box, understand the market needs, and design a framework that is easy to learn but solves the complexities of web development.

Laravel is a well-structured framework with solid design principles and streamlined codes. It constitutes interchangeable components and is mostly based on Symfony 2.

Even as a novice Laravel developer at Laravel website development services, you can easily understand the defined and clear concepts because the framework is thoroughly documented.  

It also hosts annual conventions in Europe and the United States or even Online for acknowledging the global audience.  

Laravel has an elegant syntax that makes the development process creative and enjoyable. Laravel packages are well-known because they won’t allow you to compromise on application functionality and allows developers to perform custom operations.

With the release of the new version 5.8.14 Laravel introduced a new feature, job-based retry delay and partial revert of the ability to register custom Doctrine DBAL types in schema builder.

Jobs defined may have different failure retry rates due to third-party API limits and various other reasons.

Primarily, retry delays were determined at the worker level only. The –delay option was used on the worker’s command.

The new update will allow the lined-up jobs to find out their own retry delay rate.  You can incorporate this using a simple retryAfter property on the job class.

If there is an involvement of more complex logic, you can define a retry after method to find out the retry delay. The method may end up returning an integer or a DateTime.

// Using a property...

public $retryAfter = 10;

// Using a method...

public function retryAfter()

{

    // ... logic

    return now()->addSeconds($seconds);

}

The logic returns the timestamp seconds until the defined DateTime is used as a delay.

Below is the list of things that are covered with the new version:

Changed:

• It allows us to use the @error blade directive at auth stubs.
• You can convert email data tables to layout tables that will improve accessibility.

Reverted:

• The version partially reverted the ability to register custom Doctrine DBAL.

Refactoring:

• Code replacement using Null Coalescing Operator is also possible.

The news about the updates is shared by many reputed Laravel web application development companies. One can also reach out to them and avail the updates at the earliest.