README

This package provides an opinionated approach to implement Pub/Sub messaging in Laravel using RabbitMQ.

Installation

Install the package via composer:

composer require hyperlab/laravel-pubsub-rabbitmq

Publish the config/pubsub.php config file:

php artisan vendor:publish --provider="Hyperlab\LaravelPubSubRabbitMQ\PubSubServiceProvider" --tag="pubsub-rabbitmq-config"

Publish the routes/subscriptions.php routes file:

php artisan vendor:publish --provider="Hyperlab\LaravelPubSubRabbitMQ\PubSubServiceProvider" --tag="pubsub-rabbitmq-subscriptions"

Add the following snippet to your application's config/queue.php file.

<?php

return [

    // ...

    'connections' => [

        // ...
        
        'pubsub' => [
            'driver' => 'pubsub',
            'hosts' => [
                [
                    'host' => env('RABBITMQ_HOST', '127.0.0.1'),
                    'port' => env('RABBITMQ_PORT', 5672),
                    'user' => env('RABBITMQ_USER', 'guest'),
                    'password' => env('RABBITMQ_PASSWORD', 'guest'),
                    'vhost' => env('RABBITMQ_VHOST', '/'),
                ],
            ],
            'options' => [
                'ssl_options' => [
                    'cafile' => env('RABBITMQ_SSL_CAFILE'),
                    'local_cert' => env('RABBITMQ_SSL_LOCALCERT'),
                    'local_key' => env('RABBITMQ_SSL_LOCALKEY'),
                    'verify_peer' => env('RABBITMQ_SSL_VERIFY_PEER', true),
                    'passphrase' => env('RABBITMQ_SSL_PASSPHRASE'),
                ],
            ],
        ],

    ],
    
    // ...
    
];

More details about the configuration options for the queue connection can be found in the readme of the vyuldashev/laravel-queue-rabbitmq package.

Configuration

You can configure the package to suit your needs through the config/pubsub.php config file. By default, the file looks like this:

<?php

return [

    'rabbitmq' => [

        /*
         * The name of the RabbitMQ exchange on which the outgoing messages are published.
         */
        'exchange' => env('PUBSUB_RABBITMQ_EXCHANGE'),

        /*
         * The name of the RabbitMQ queue from which the incoming messages are consumed.
         */
        'queue' => env('PUBSUB_RABBITMQ_QUEUE'),

    ],

    'queue' => [

        /*
         * The queue connection that is used to communicate with RabbitMQ.
         */
        'connection' => env('PUBSUB_QUEUE_CONNECTION', 'pubsub'),
        
        /*
         * The queue worker that you want to consume your incoming messages with.
         *
         * Valid options are: default, horizon
         */
        'worker' => env('PUBSUB_QUEUE_WORKER', 'default'),

    ],

    /*
     * The file within your code base that contains the message subscriptions of your application.
     */
    'subscriptions' => base_path('routes/subscriptions.php'),

];

Subscribers

In order for your application to receive messages from RabbitMQ, it needs to subscribe to one or more message types.

By default, these subscriptions can be defined in the routes/subscriptions.php file. However, the path to this file can be changed in the configuration file.

The contents of the subscriptions file should look like this:

<?php

return [

    'user.created' => HandleUserCreatedMessage::class,

    'user.deleted' => [HandleUserDeletedMessage::class, 'handle'],

];

The file returns an associative array in which:

• a key represents a type of messages that the application wants to receive
• a value represents the class within your application that handles the incoming message of this type

The handler of a subscription can be defined in two ways:

1. By referencing a class

   'user.created' => HandleUserCreatedMessage::class,

   In this case, the package looks for a public method in the class that accepts a Hyperlab\LaravelPubSubRabbitMQ\Subscriber\Message as argument. This method can be called anything, as shown here:

   class HandleUserCreatedMessage
   {
       public function __invoke(\Hyperlab\LaravelPubSubRabbitMQ\Subscriber\Message $message): void
       {
           //
       }
   }
   
   class HandleUserCreatedMessage
   {
       public function handle(\Hyperlab\LaravelPubSubRabbitMQ\Subscriber\Message $message): void
       {
           //
       }
   }
   
   class HandleUserCreatedMessage
   {
       public function execute(\Hyperlab\LaravelPubSubRabbitMQ\Subscriber\Message $message): void
       {
           //
       }
   }

2. By referencing a class and method

   'user.created' => [HandleUserCreatedMessage::class, 'handle'],

Testing

composer test

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Hyperlab
• All Contributors

License

The MIT License (MIT). Please see License File for more information.