RabbitMQ Support

Asynchronous PHP RabbitMQ
Installation
composer require ecotone/amqp
Module Powered By
​Enqueue solid and powerful abstraction over asynchronous queues.
Configuration
In order to use AMQP Support we need to add ConnectionFactory to our Dependency Container. 
Symfony
Laravel
Symfony
# config/services.yaml
# You need to have RabbitMQ instance running on your localhost, or change DSN
    Enqueue\AmqpLib\AmqpConnectionFactory:
        class: Enqueue\AmqpLib\AmqpConnectionFactory
        arguments:
            - "amqp://guest:[email protected]:5672//"
Laravel
# Register AMQP Service in Provider
​
use Enqueue\AmqpLib\AmqpConnectionFactory;
​
public function register()
{
     $this->app->singleton(AmqpConnectionFactory::class, function () {
         return new AmqpConnectionFactory("amqp+lib://guest:[email protected]:5672//");
     });
}
We register our AmqpConnection under the class name Enqueue\AmqpLib\AmqpConnectionFactory. This will help Ecotone resolve it automatically, without any additional configuration.
Message Channel
To create AMQP Backed Message Channel (RabbitMQ Channel), we need to create Service Context. 
class MessagingConfiguration
{
    #[ServiceContext] 
    public function orderChannel()
    {
        return AmqpBackedMessageChannelBuilder::create("orders");
    }
}
Now orders channel will be available in our Messaging System. 
Distributed Publisher and Consumer
To create distributed publisher or consumer provide Service Context.
Distributed Publisher
class MessagingConfiguration
{
    #[ServiceContext] 
    public function distributedPublisher()
    {
        return AmqpDistributedBusConfiguration::createPublisher();
    }
}
Distributed Consumer
class MessagingConfiguration
{
    #[ServiceContext] 
    public function distributedPublisher()
    {
        return AmqpDistributedBusConfiguration::createConsumer();
    }
}
Custom Message Publisher
Available actions
interface MessagePublisher
{
​
    // 1
    public function send(string $data, string $sourceMediaType = MediaType::TEXT_PLAIN) : void;
​
    // 2
    public function sendWithMetadata(string $data, array $metadata, string $sourceMediaType = MediaType::TEXT_PLAIN) : void;
​
    // 3
    public function convertAndSend(object|array $data) : void;
​
​
    // 4
    public function convertAndSendWithMetadata(object|array $data, array $metadata) : void;
}
send - Send a string type via Publisher. It does not need any conversion, you may add additional Media Type of $data.
sendWithMetadata - Does the same as send, allows for sending additional Meta data.
convertAndSend - Allow for sending types, which needs conversion. Allow for sending objects and array, Ecotone make use of Conversion system to convert $data.
convertAndSendWithMetadata - Does the same as convertAndSend, allow for sending additional Meta data.
Configuration
If you want to publish Message directly to Exchange, you may use of Publisher.
class AMQPConfiguration
{
    #[ServiceContext] 
    public function registerAmqpConfig()
    {
        return 
            AmqpMessagePublisherConfiguration::create(
                Publisher::class, // 1
                "delivery", // 2
                "application/json" // 3
            );
    }
}
Reference name -  Name under which it will be available in Dependency Container.
Exchange name - Name of exchange where Message should be publisher
Default Conversion [Optional] - Default type, payload will be converted to.
Publisher is a special type of Gateway, which implements Publisher interface.
It will be available in your Dependency Container under passed Reference name.
In case interface name Publisher:class is used, it will be available using auto-wire.
#[EventHandler] 
public function whenOrderWasPlaced(OrderWasPlaced $event, Publisher $publisher) : void
{
    $publisher->convertAndSendWithMetadata(
        $event,
        [
            "system.executor" => "Johny"
        ]
    );
}
Additional Publisher Configuration
RegisterAmqpPublisher::create(
    Publisher::class,
    "delivery"
)
    ->withDefaultPersistentDelivery(true) // 1
    ->withDefaultRoutingKey("someKey") // 2
    ->withRoutingKeyFromHeader("routingKey") // 3
    ->withHeaderMapper("application.*") // 4
withDefaultPersistentDelivery - should AMQP messages be persistent.
withDefaultRoutingKey - default routing key added to AMQP message 
withRoutingKeyFromHeader - should routing key be retrieved from header with name
withHeaderMapper - On default headers are not send with AMQP message. You map provide mapping for headers that should be mapped to AMQP Message
Consumer
To connect consumer directly to a AMQP Queue, we need to provide Ecotone with information, how the Queue is configured. 
class AmqpConfiguration
{
    #[ServiceContext] 
    public function registerAmqpConfig(): array
    {
        return [
            AmqpQueue::createWith("orders"), // 1
            AmqpExchange::createDirectExchange("system"), // 2
            AmqpBinding::createFromNames("system", "orders", "placeOrder"), // 3
        ];
    }
}
AmqpQueue::createWith(string $name) - Registers Queue with specific name
AmqpExchange::create*(string $name) - Registers of given type with specific name
AmqpBinding::createFromName(string $exchangeName, string $queueName, string $routingKey)- Registering binding between exchange and queue
When we do have registered configuration, we can register Consumer for specific queue.
class Consumer
{
    #[AmqpChannelAdapter(
        endpointId: "amqp_consumer",  // 1
        queueName: "queue_name",  // 2
        headerMapper: "application.*" // 3 
    )] 
    public function execute(string $message) : void
    {
        // do something with Message
        // if you have converter registered you can type hint exact type you expect
    }
}
endpointId - Defines identifier for this consumer. It will be available under this name to run
ecotone:list
+--------------------+
| Endpoint Names     |
+--------------------+
| amqp_consumer      |
+--------------------+
  2. queueName - The queue name which will be polled by this consumer
  3. headerMapper - Headers which should be mapped to Message 
Publisher Transactions
Ecotone AMQP comes with support for RabbitMQ Transaction for published messages. 
To enable transactions on specific endpoint, mark it with Ecotone\Amqp\AmqpTransaction\AmqpTransaction annotation.
    #[AmqpChannelAdapter(endpointId: "amqp_consumer",queueName: "queue_name") 
    #[AmqpTransaction)
    public function execute(string $message) : void
    {
        // do something with Message
    }
If you want to enable/disable for all Asynchronous Endpoints or specific for Command Bus. You may use of ServiceContext. 
By default all transactions are enabled
class ChannelConfiguration
{
    #[ServiceContext]
    public function registerTransactions() : array
    {
        return [
            AmqpConfiguration::createWithDefaults()
                ->withTransactionOnAsynchronousEndpoints(false)
                ->withTransactionOnCommandBus(false)
        ];
    }
​
}
Modules - Previous
JMS Converter
Next - Modules
DBAL Support
Last updated 3 months ago