Laravel Queues in Action is now available!

Dispatching Unique Jobs to Laravel Queues

Updated: Oct 25, 2020 — 1 min Read#queues

Here's the problem we are trying to solve:

Each time a product is updated, we want to dispatch a job that updates the search index. If several products were updated during a short period of time, we don't want to dispatch multiple jobs. There should be only a single index update job in the queue at any time.

To solve this problem, we are going to use cache locks to prevent dispatching UpdateProductsIndex jobs while another instance of the job is in the queue. So in the controller's update method, we're going to dispatch the job only if a lock was successfully acquired:

public function update($product)

    $lock = Cache::lock('productsIndex', 120);

    if ($lock->get()) {

This lock will hold for 120 seconds, you may update that to a value that makes sense in your use case.

Now inside the handle method of the job, we're going to release the lock after the job finishes:

public function handle()
    // Update the search index

Notice here we use forceRelease() on the lock because we don't care who the lock owner is. For more information about this, check the official laravel documentation.

We may also release the lock inside the failed method of the job class:

public function failed(Throwable $exception)

With these simple changes, we made sure only a single UpdateProductsIndex job will be in the queue at any point in time.

Hey! 👋 If you want to receive updates on what I'm up to, I host a newsletter on my website and would love to have you.

You can also follow me on Twitter, I regularly post about all things Laravel including my latest video tutorials and blog posts.

By Mohamed Said

Hello! I'm a full-stack web developer working at Laravel. In this publication, I share everything I know about Laravel's core, packages, and tools.

You can find me on Twitter and Github.

This site was built using Wink. Follow the RSS Feed.