Runax.Messaging.Transports.RabbitMq 2.0.0

Runax.Messaging.Transports.RabbitMq

RabbitMQ transport for Runax.Messaging. Topics map to routing keys on a topic exchange.

Built against RabbitMQ.Client 7.x (the asynchronous IChannel API).

Install

dotnet add package Runax.Messaging
dotnet add package Runax.Messaging.Transports.RabbitMq

Register

Attach the transport to a bus with its config object:

using Runax.Messaging;
using Runax.Messaging.Transports.RabbitMq;

builder.Services.AddRunaxMessaging(messaging =>
{
    messaging.AddBus(bus =>
    {
        bus.AddTransport(new RabbitMqConfig
        {
            HostName = "localhost",
        });
        bus.AddConsumer<OrderPlacedConsumer>();
    });
});

RabbitMqConfig lives in the Runax.Messaging.Transports.RabbitMq namespace, so add that using. The config is validated at startup (DataAnnotations, when the AddBus block completes); bind it from an IConfiguration section instead of setting properties: bus.AddTransport<RabbitMqConfig>(builder.Configuration.GetSection("RabbitMq")).

Config

Set these directly on RabbitMqConfig.

Beyond the transport config, settings from the core package apply to the bus that runs this transport — AddConsumer<T>(), WithRetry(...), OnUnroutableMessage(...), ConfigureSerialization(...), and UseSerializer<T>() — all inside the same AddBus block. Two RabbitMQ clusters are simply two buses, each with its own RabbitMqConfig. See Configuration & per-bus settings.

Behavior

• Publish sends the serialized envelope to ExchangeName using the topic as the routing key, with persistent delivery. Publishes fan out across a pool of channels (PublishChannelPoolSize) and, when PublisherConfirms is on, wait for broker confirmation. Automatic and topology recovery are enabled. A ConsumeOnly bus creates no publish channel pool.
• Batch publish (PublishBatchAsync) publishes all envelopes on one channel and waits for a single confirm for the whole batch instead of one per message.
• Subscribe declares an exclusive, auto-delete queue (with BasicQos prefetch), binds it to each topic, and maps the dispatch verdict to the broker:
  • Acknowledge → basic.ack
  • Requeue → basic.nack with requeue
  • DeadLetter → basic.nack without requeue, routed to DeadLetterExchange when configured (otherwise dropped by the broker)

To use RabbitMQ's native dead-lettering, set DeadLetterExchange and configure bus.WithRetry(o => o.Strategy = DeadLetterStrategy.BrokerNative) on the bus.

Health check

A broker-reachability check named runax:{bus} is registered automatically for each bus that runs this transport. Opt out per bus:

bus.AddTransport(new RabbitMqConfig { HostName = "localhost", RegisterHealthCheck = false });

Telemetry

The transport reports messaging.system = "rabbitmq" on the spans and metrics emitted by the core package (activity source / meter "Runax.Messaging"); the messaging.runax.bus tag identifies the bus.

License

MIT