redb.Route.Sqs 3.3.2

redb.Route.Sqs

Amazon SQS + SNS transport for redb.Route, via the native AWS SDK for .NET v4 (AWSSDK.SQS, AWSSDK.SimpleNotificationService). One package, two schemes — sqs:// (queue: consume + produce) and sns:// (topic: publish + SNS→SQS fan-out). LocalStack / ElasticMQ compatible.

Installation

dotnet add package redb.Route.Sqs

services.AddRedbRoute(route =>
{
    route.Services.AddRedbRouteSqs();   // registers sqs:// and sns://
    route.AddRouteBuilder<MyRoutes>();
});

Usage

using redb.Route.Sqs.Fluent;

// Consume a queue — long-poll, 4 competing consumers, delete after processing
From(Sqs.Queue("orders").WaitTimeSeconds(20).ConcurrentConsumers(4))
    .Process(HandleOrder);

// Produce to a queue
To(Sqs.Queue("orders").Region("eu-west-1"));

// FIFO queue (name ends in .fifo) — group id required
To(Sqs.Queue("orders.fifo").MessageGroupId("${header.customerId}"));

// Publish to an SNS topic
To(Sns.Topic("events").Region("us-east-1"));

// SNS → SQS fan-out: subscribe a queue, then consume it with sqs://
To(Sns.Topic("events").SubscribeSnsToSqs("arn:aws:sqs:us-east-1:000000000000:events-q"));

// Same, but raw delivery — the queue gets the bare payload (no SNS JSON envelope),
// and SNS attributes arrive as SQS attributes (so trace context survives the hop):
To(Sns.Topic("events")
    .SubscribeSnsToSqs("arn:aws:sqs:us-east-1:000000000000:events-q")
    .RawMessageDelivery());

Envelope vs raw. By default SNS wraps the payload in a JSON notification envelope ({"Type":"Notification","Message":"<payload>",...}), so the subscribing queue receives the envelope, not your payload — and SNS message attributes are buried inside it. Add .RawMessageDelivery() (sets RawMessageDelivery=true on the auto-created subscription) to get the bare payload and have SNS attributes map to SQS message attributes. It applies only to the subscribeSnsToSqs auto-subscription; the default stays false (AWS-compatible envelope).

Raw URIs work too: sqs://orders?waitTimeSeconds=20&concurrentConsumers=4, sns://events?region=us-east-1.

Concurrency & delivery

• concurrentConsumers=N runs N competing receive loops — up to N messages processed in parallel (the SQS-native model). See the framework-wide Concurrency & Parallelism guide (CONCURRENCY.md) for how this compares to the .Threads(N) processing EIP.
• At-least-once: a message is deleted only after it processes successfully. On failure it is left for redelivery after the visibility timeout (or reset to 0 immediately with resetVisibilityOnFailure=true).
• extendMessageVisibility=true keeps a message hidden while a long handler runs (heartbeat).
• transacted=true defers the delete into the route transaction (.Transacted()), committing / rolling back together with redb DB work.
• Ordering is preserved only per FIFO message group and only with concurrentConsumers=1.

Key options

Part of

Part of the redb.Route enterprise integration framework.