Runax.Messaging.Transports.Aws.Sqs 2.0.0

Runax.Messaging.Transports.Aws.Sqs

Amazon SQS transport for Runax.Messaging. Topics map to SQS queues (by name, or by an explicit queue-URL mapping).

Install

dotnet add package Runax.Messaging
dotnet add package Runax.Messaging.Transports.Aws.Sqs

Register

Attach the transport to a bus with its config object:

using Runax.Messaging;
using Runax.Messaging.Transports.Aws.Sqs;

builder.Services.AddRunaxMessaging(messaging =>
{
    messaging.AddBus(bus =>
    {
        bus.AddTransport(new SqsConfig
        {
            Region = "us-east-1",
        });
        bus.AddConsumer<OrderPlacedConsumer>();
    });
});

SqsConfig lives in the Runax.Messaging.Transports.Aws.Sqs 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<SqsConfig>(builder.Configuration.GetSection("Sqs")).

Config

Set these directly on SqsConfig.

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 SQS accounts (or regions) are simply two buses, each with its own SqsConfig. See Configuration & per-bus settings.

Behavior

• Publish sends the serialized envelope to the resolved queue. Batch publish (PublishBatchAsync) uses SendMessageBatch, chunked at the SQS limit of 10 per call.
• Subscribe runs one pump per queue in parallel and dispatches messages continuously, bounded by MaxConcurrentMessages (so successive polls overlap rather than draining one batch at a time). Each message maps the dispatch verdict to the queue:
  • Acknowledge → DeleteMessage
  • Requeue and DeadLetter → leave the message so its visibility timeout lapses and SQS redelivers it, routing to a configured redrive DLQ once maxReceiveCount is reached
• While a message is being handled, the transport extends its visibility timeout (ExtendVisibilityDuringProcessing) so in-process retry backoff does not let it reappear on the queue.

For native dead-lettering, configure a redrive policy on the queue and set bus.WithRetry(o => o.Strategy = DeadLetterStrategy.BrokerNative) on the bus.

Health check

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

bus.AddTransport(new SqsConfig { Region = "us-east-1", RegisterHealthCheck = false });

Telemetry

The transport reports messaging.system = "sqs" 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