Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Async Bundle Laravel Package

dubture/async-bundle

View on GitHub
Deep Wiki
Context7

Async Bundle

Build Status Scrutinizer Code Quality

This Symfony bundle provides a high-level way of sending expensive logic to background workers.

Configuration

  1. Install the bundle using composer require "dubture/async-bundle"
  2. Add the necessary bundles to your Kernel:
// app/AppKernel.php

public function registerBundles()
{
    $bundles = array(

        // register the async bundle
        new Dubture\AsyncBundle\DubtureAsyncBundle(),

        // register the dependencies of the async bundle
        new JMS\DiExtraBundle\JMSDiExtraBundle($this),
        new JMS\AopBundle\JMSAopBundle(),

        // your application bundles here...

    );

    return $bundles;
}
  1. Configure which backend to use:
# app/config/config.yml
dubture_async:
  backend: rabbitmq # one of rabbitmq|resque|sonata|runtime

Usage

Consider the following service:

<services>
    <service class="Acme\Bundle\MediaTranscodingService" id="media_transcoder">
    </service>
</services>

class MediaTranscodingService
{
    public function transcodeFile($sourcePath)
    {
            // ... do some heavy-lifting, e.g. media transcoding
    }
}

If you want to delegate this method to a background worker, this is all you need to do:


use Dubture\AsyncBundle\Annotation\Async;

class MediaTranscodingService
{
    /**
     * @Async
     */
    public function transcodeFile($sourcePath)
    {
            // ... do some heavy-lifting, e.g. media transcoding
    }
}

Now any call to transcodeFile will be intercepted and delegated to a background worker.

Methods annotated with @Async need to adhere to the following contract:

  1. The class declaring the async method must be a service
  2. The methods arguments must be serializable (no resources, e.g. doctrine connections)
  3. The method should not return anything (any return value will be lost)

If you need to react to something happening inside your background worker, you can simply dispatch events when it's done.

The background-worker implementation relies on one of the following bundles:

See Resources/docs for documentation of the specific backends.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
steadrun/laravel-monitor
labyrinthe/connect-laravel
elmogy/layan
drewdan/sentinel-client
dskripchenko/laravel-llm
fatryst/nuonuo
stevenay/myanfont
gmostafa/php-graphql-client
xeviant/paystack
snowsoft/faker
meditationsteps/blogetc
animalyoung/laravel-influxdb
onix-solutions/sms-telera
lonely-lights/prosetta
oxygen/data
oxygen/core
jengo/base
xiloryx/log-collector
a21ns1g4ts/filament-stripe
la-php/laravel-admin