texthtml/pimple-rabbitmq-provider

Silex service provider for RabbitMQ. Integrates php-amqplib/rabbitmq-bundle into Silex.

Maintainers

Details

github.com/texthtml/pimple-rabbitmq-provider

Homepage

Source

Issues

Installs: 90

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Watchers: 2

Forks: 0

Open Issues: 0

v1.0.0 2016-12-05 09:11 UTC

Requires

Requires (Dev)

MIT ce676cd516d836d206371e858518c5ef03336430

silexqueuerabbitmqmessageAMQPproviderpimple

This package is auto-updated.

Last update: 2024-03-24 18:19:51 UTC

README

About

This Pimple service provider incorporates the awesome RabbitMqBundle into your application. Installing this bundle created by Alvaro Videla you can use RabbitMQ messaging features in your application, using the php-amqplib library.

After installing this service provider, sending messages from a controller would be something like

$app->post('/message', function(Request $request) use ($app){
    $producer = $app['rabbit.producer']['my_exchange_name'];
    $producer->publish('Some message');

    return new Response($msg_body);
});

Later when you want to consume 50 messages out of the queue names 'my_queue', you just run on the CLI:

$ ./app/console rabbitmq:consumer -m 50 my_queue

To learn what you can do with the bundle, please read the bundle's README.

Installation

Require the library with Composer:

$ composer require texthtml/pimple-rabbitmq-provider

Then, to activate the service, register the service provider after creating your Pimple Container. With Silex 2:

use Silex\Application;
use TH\RabbitmqProvider\RabbitServiceProvider;

$app = new Application();
$app->register(new RabbitServiceProvider());

Start sending messages ;)

Usage

In the README file from the Symfony bundle you can see all the available options. For example, to configure our service with two different connections and a couple of producers, and one consumer, we will pass the following configuration:

$app->register(new RabbitServiceProvider(), [
    'rabbit.connections' => [
        'default' => [
            'host'      => 'localhost',
            'port'      => 5672,
            'user'      => 'guest',
            'password'  => 'guest',
            'vhost'     => '/'
        ],
        'another' => [
            'host'      => 'another_host',
            'port'      => 5672,
            'user'      => 'guest',
            'password'  => 'guest',
            'vhost'     => '/'
        ]
    ],
    'rabbit.producers' => [
        'first_producer' => [
            'connection'        => 'another',
            'exchange_options'  => ['name' => 'a_exchange', 'type' => 'topic']
        ],
        'second_producer' => [
            'connection'        => 'default',
            'exchange_options'  => ['name' => 'a_exchange', 'type' => 'topic']
        ],
    ],
    'rabbit.consumers' => [
        'a_consumer' => [
            'connection'        => 'default',
            'exchange_options'  => ['name' => 'a_exchange','type' => 'topic'],
            'queue_options'     => ['name' => 'a_queue', 'routing_keys' => ['foo.#']],
            'callback'          => 'your_consumer_service'
        ]
    ]
]);

Keep in mind that the callback that you choose in the consumer needs to be a service that has been registered in the Pimple container. Consumer services implement the ConsumerInterface, which has a execute() public method.

Credits