A bundle to use swarrot inside your Symfony2 application

The recommended way to install this bundle is through Composer. Require the swarrot/swarrot-bundle package into your composer.json file:

{
    "require": {
        "swarrot/swarrot-bundle": "@stable"
    }
}

Protip: you should browse the swarrot/swarrot-bundle page to choose a stable version to use, avoid the @stable meta constraint.

Update app/AppKernel.php:

public function registerBundles()
{
    $bundles = array(
        // ...
        new Swarrot\SwarrotBundle\SwarrotBundle(),
    );

    return $bundles;
}

swarrot:
    provider: pecl # pecl or amqp_lib
    default_connection: rabbitmq
    default_command: swarrot.command.base # Swarrot\SwarrotBundle\Command\SwarrotCommand
    connections:
        rabbitmq:
            host: "%rabbitmq_host%"
            port: "%rabbitmq_port%"
            login: "%rabbitmq_login%"
            password: "%rabbitmq_password%"
            vhost: '/'
    processors_stack:
        signal_handler: 'Swarrot\Processor\SignalHandler\SignalHandlerProcessor'
        ack: 'Swarrot\Processor\Ack\AckProcessor'
        max_messages: 'Swarrot\Processor\MaxMessages\MaxMessagesProcessor'
        retry: 'Swarrot\Processor\Retry\RetryProcessor'
        exception_catcher: 'Swarrot\Processor\ExceptionCatcher\ExceptionCatcherProcessor'
        max_execution_time: 'Swarrot\Processor\MaxExecutionTime\MaxExecutionTimeProcessor'
    consumers:
        my_consumer:
            processor: my_consumer.processor.service
            extras:
                poll_interval: 500000
                retry_exchange: my_consumer_exchange
                retry_attempts: 3
                retry_routing_key_pattern: 'retry_%%attempt%%'
    messages_types:
        my_publisher:
            connection: rabbitmq # use the default connection by default
            exchange: my_exchange
            routing_key: my_routing_key

First step is to retrieve the swarrot publisher service from your controller.

$messagePublisher = $this->get('swarrot.publisher');

After you need to prepare your message with the Message class.

use Swarrot\Broker\Message;

$message = new Message('"My first message with the awesome Swarrot lib :)"');

Then you can publish a new message into a predefined configuration (connection, exchange, routing_key, etc.) from your message_types.

$messagePublisher->publish('webhook.send', $message);

When publishing a message you can override the message_types configuration by passing a third argument:

$messagePublisher->publish('webhook.send', $message, array(
    'exchange'    => 'my_new_echange',
    'connection'  => 'my_second_connection',
    'routing_key' => 'my_new_routing_key'
));

Swarrot will automatically create new commands according to your configuration. This command need the queue name to consume as first argument. You can also use a named connection as second argument if you don't want to use the default one.

app/console swarrot:consume:my_consumer_name queue_name [connection_name]

Your processor will automatically be decorated by all processors named in the processors_stack section. No matter the order you list your processors, here is the default order:

• SignalHandler
• ExceptionCatcher
• MaxMessages
• MaxExecutionTime
• Ack
• Retry

All this processors are configurable. You can add extras key on each consumer definition in your config.yml

swarrot:
    ...
    consumers:
        my_consumer:
            processor: my_consumer.processor.service
            extras:
                poll_interval: 500000
                requeue_on_error: 1
                max_messages: 10
                retry_exchange: my_consumer_exchange
                retry_attempts: 3
                retry_routing_key_pattern: 'retry_%%attempt%%'

You can also use options of the commande line:

• --poll-interval [default: 500000]: Change the polling interval when no message found in broker
• --requeue-on-error (-r): Re-queue the message in the same queue if an error occurred.
• --no-catch (-C): Disable the ExceptionCatcher processor (available only if the processor is in the stack)
• --max-execution-time (-t) [default: 300]: Configure the MaxExecutionTime processor (available only if the processor is in the stack)
• --max-messages (-m) [default: 300]: Configure the MaxMessages processor (available only if the processor is in the stack)
• --no-retry (-R): Disable the Retry processor (available only if the processor is in the stack)

Default values will be override by your config.yml and use of options will override defaut|config values.

If you want to implement your own provider (like Redis). First, you have to implements the Swarrot\SwarrotBundle\Broker\FactoryInterface. Then, you can register it with along the others services and tag it with swarrot.provider_factory.

services:
    app.swarrot.custom_provider_factory:
        class: AppBundle\Provider\CustomFactory
        tags:
            - {name: swarrot.provider_factory}
    app.swarrot.redis_provider_factory:
        class: AppBundle\Provider\RedisFactory
        tags:
            - {name: swarrot.provider_factory, alias: redis}

Now you can tell to swarrot to use it in the config.yml file.

swarrot:
  provider: app.swarrot.custom_provider_factory
  ...

or with the alias

swarrot:
  provider: redis
  ...

If you use Swarrot you may not want to realy publish messages like in test environment for example. You can use the BlackholePublisher to achieve this.

Simply override the swarrot.publisher.class parameter in the DIC with the Swarrot\SwarrotBundle\Broker\PublisherBlackhole class.

Update config_test.yml for example:

parameters:
    swarrot.publisher.class: Swarrot\SwarrotBundle\Broker\BlackholePublisher

This bundle is released under the MIT License. See the bundled LICENSE file for details.