Flowly.RabbitMQ 1.5.0

dotnet add package Flowly.RabbitMQ --version 1.5.0
                    
NuGet\Install-Package Flowly.RabbitMQ -Version 1.5.0
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Flowly.RabbitMQ" Version="1.5.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Flowly.RabbitMQ" Version="1.5.0" />
                    
Directory.Packages.props
<PackageReference Include="Flowly.RabbitMQ" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Flowly.RabbitMQ --version 1.5.0
                    
#r "nuget: Flowly.RabbitMQ, 1.5.0"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Flowly.RabbitMQ@1.5.0
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Flowly.RabbitMQ&version=1.5.0
                    
Install as a Cake Addin
#tool nuget:?package=Flowly.RabbitMQ&version=1.5.0
                    
Install as a Cake Tool

Flowly.RabbitMQ

RabbitMQ transport for Flowly. Swap this for Flowly.AzureServiceBus without changing any handler or sender code.

Quick Start

// Program.cs — connection string key from appsettings.json
builder.AddFlowly(configure => configure
    .UseRabbitMq("RabbitMQ")
    .AddMessageHandler<OrderCreated, OrderCreatedHandler>()
    .AddMessageSubmitter<OrderCreated>());
// appsettings.json
{
  "ConnectionStrings": {
    "RabbitMQ": "amqp://guest:guest@localhost:5672/"
  }
}

The default connection string (amqp://guest:guest@localhost:5672/) is used when no configuration key is provided.

Health Check

builder.AddFlowly(configure => configure
    .UseRabbitMq("RabbitMQ", enableHealthCheck: true));

Registers a health check under the tag "rabbitmq".

Retry Topology

Flowly's retry mechanism uses a {queue}.retry queue with RabbitMQ's Dead Letter Exchange. With the default createTopology: true, the retry queue, DLX, and dead letter queue are created automatically at startup. No manual configuration required.

Stream start positions and checkpoints

When a MessageStreamCheckpoint<T> is registered and holds no position for a reader, StartPosition.Last() and StartPosition.Timestamp(...) are resolved to a concrete offset and stored before consumption starts. RabbitMQ has no AMQP call for that, so the client attaches a short-lived probe consumer (a dedicated channel on the consumer connection, no Stream protocol port needed; for a partitioned stream, one per partition stream) at the last chunk or at the timestamp and reads the x-stream-offset of what it is delivered. A first start therefore takes about 0.3 s longer when the stream holds messages and about 1 s longer when the stream (or partition) is empty. If the broker cannot answer, the position is stored after the first processed batch instead.

Partitioned stream recovery

When the start position of a partition of a partitioned stream cannot be resolved (for example the MessageStreamCheckpoint<T> store is unavailable while the partition is assigned), Flowly retries the resolution for up to 40 seconds, so a short outage drops nothing. If the partition is still unresolved, it is reported as Waiting (see the root README.md), the messages the broker's client still delivers for it are dropped and counted (flowly.message.stream.partition.dropped, with a log summary at most every 30 seconds instead of a warning per message), and the Stream consumer is recreated automatically with a growing delay (5 seconds doubling up to 2 minutes) until the partition resolves. The healthy partitions are re-initialized from their checkpoints by each recreation and the batch they were processing is delivered again, so handlers must be idempotent. After 3 consecutive recreations that still leave a partition waiting, the instance stands down: it keeps its consumer closed for a cool-down (1 minute, doubling to 5 minutes) so the broker can hand the partitions to another instance that may be able to resolve them, then creates it again; an instance that is alone still recovers after every cool-down but consumes nothing while it lasts. The stand-down is logged and counted in flowly.message.stream.partition.stand_downs. Nothing is skipped: after the partition starts, everything since the stored position is delivered.

Local Development

dotnet tool install --global Flowly.Tool
flowly docker-compose --project ./MyService --output docker-compose.yml
docker compose up -d

Documentation

Full guide including retry topology, events, and multi-provider configuration: https://rasmustherkelsen.github.io/flowly/

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.5.0 49 11/20/2026
1.4.4 167 8/27/2026
1.4.3 146 8/13/2026
1.4.2 134 8/13/2026
1.4.1 131 8/11/2026
1.4.0 142 8/11/2026
1.3.2 147 7/3/2026
1.3.1 143 6/26/2026
1.3.0 142 6/24/2026
1.2.0 176 5/27/2026
1.1.1 140 5/22/2026
1.1.0 155 5/18/2026
1.0.1 135 5/6/2026
1.0.0 123 5/6/2026