Stratara.Outbox.AzureServiceBus
4.4.10
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Outbox.AzureServiceBus --version 4.4.10
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 4.4.10
<PackageReference Include="Stratara.Outbox.AzureServiceBus" Version="4.4.10" />
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="4.4.10" />
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
paket add Stratara.Outbox.AzureServiceBus --version 4.4.10
#r "nuget: Stratara.Outbox.AzureServiceBus, 4.4.10"
#:package Stratara.Outbox.AzureServiceBus@4.4.10
#addin nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.4.10
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.4.10
Stratara.Outbox.AzureServiceBus
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Azure Service Bus implementation of Stratara.Abstractions.Messaging.IMessageBus. Publishes JSON-serialized messages to topics and exposes a subscription helper that wires up a Service Bus processor with per-message exception classification:
- success →
CompleteMessageAsync ConcurrencyException→AbandonMessageAsyncuntilMessageRetry:MaxConflictRequeuesredeliveries (default 100) have not resolved it, thenDeadLetterMessageAsyncwith reasonconflict- any other exception →
AbandonMessageAsyncuntilMessageRetry:MaxDeliveryAttemptsdeliveries (default 3) have failed, thenDeadLetterMessageAsyncwith reasonfailureand the exception in the description
The subscription's own MaxDeliveryCount must leave room for the bounds; a subscription created with Service Bus defaults allows 10 deliveries. Where the host can read the subscription, the bus lowers the bounds for it to fit and logs 108_111.
System-level errors (connection drops, auth failures) arrive via ProcessErrorAsync and are logged; the Service Bus client owns the reconnect / retry policy for those.
A subscription that stops closes its processor, which takes no further message and waits for its running handler — as long as the host's shutdown timeout allows while the application stops, twenty seconds otherwise; the host waits for that before it counts as stopped. A handler that gives up because the subscription stops has its message abandoned rather than dead-lettered by the framework; the broker counts that delivery like any other. A handler's outcome is settled whatever the subscription's own cancellation says, and a handler that failed because its save committed but could not publish has its message completed, not delivered again.
Install
dotnet add package Stratara.Outbox.AzureServiceBus
Register the bus in your DI composition — one call wires the ServiceBusClient, the envelope
options and the IMessageBus implementation:
// Connection string:
builder.Services.AddAzureServiceBus(builder.Configuration.GetConnectionString("ServiceBus")!);
// Or, preferred in Azure — managed identity, no secret in configuration:
builder.Services.AddAzureServiceBusWithManagedIdentity("my-namespace.servicebus.windows.net");
The AzureServiceBusBus implementation is internal; register it through these extensions rather
than by naming the type.
The explicitly-chosen transport wins.
AddAzureServiceBusreplaces theIMessageBusregistration, so it takes effect even when the RabbitMQ umbrella (builder.AddMessaging(), which the worker composites call) already claimed the slot. Still use one transport per host — calling both is a configuration smell — but an explicitAddAzureServiceBuswill no longer be a silent no-op behind a composite.
Notes
Pre-3.0 this implementation lived inside Stratara.Outbox.RabbitMQ. As of 3.0 the two transports are separate packages so a consumer who only wants RabbitMQ does not drag the Azure Service Bus SDK into the dependency tree (and vice versa).
| Product | Versions 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. |
-
net10.0
- Azure.Identity (>= 1.21.0)
- Azure.Messaging.ServiceBus (>= 7.21.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.13)
- Microsoft.Extensions.Options (>= 10.0.13)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.13)
- Stratara.Abstractions (>= 4.4.10)
- Stratara.Shared (>= 4.4.10)
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 |
|---|---|---|
| 4.8.0 | 103 | 11/6/2026 |
| 4.7.1 | 97 | 11/5/2026 |
| 4.7.0 | 106 | 10/30/2026 |
| 4.6.1 | 105 | 10/29/2026 |
| 4.6.0 | 102 | 10/28/2026 |
| 4.5.0 | 107 | 10/28/2026 |
| 4.4.10 | 103 | 10/26/2026 |
| 4.4.9 | 98 | 10/26/2026 |
| 4.4.8 | 100 | 10/24/2026 |
| 4.4.7 | 102 | 10/23/2026 |
| 4.4.6 | 97 | 10/22/2026 |
| 4.4.5 | 108 | 10/14/2026 |
| 4.4.4 | 107 | 10/10/2026 |
| 4.4.3 | 111 | 10/10/2026 |
| 4.4.2 | 113 | 10/2/2026 |
| 4.4.1 | 107 | 9/29/2026 |
| 4.4.0 | 109 | 9/27/2026 |
| 4.3.1 | 116 | 9/25/2026 |
| 4.3.0 | 113 | 9/23/2026 |
| 4.2.0 | 123 | 9/18/2026 |
A release for hosts on the Orleans execution model. A durable timer now answers its tick while its handler runs, so a
long handler leaves no reminder error in the silo's log, and a timer that fails is logged by the framework with its
owner and purpose. A commit no longer constructs every registered projection to learn which store readers to wake. No
API change, no schema change and no migration.
### Changed
- **A commit no longer constructs every projection.** On the Orleans execution model, every command that committed
facts constructed each registered projection, with its dependencies, only to learn the names of the store readers to
wake. The names are now worked out once per silo, and the wait for a projection, the rebuild and the full replay's
checkpoint reset use the same list. A rebuild of a name that is not registered is refused before any reader is
paused, with the same message as before.
### Fixed
- **A durable timer answers its tick while its handler runs.** On the Orleans execution model, a durable timer's
reminder call stayed open until its handler returned, so a handler longer than the runtime's response timeout made
Orleans log `Could not deliver reminder tick` at Error for every tick it outlasted. The tick is now answered at once
and the handler runs in a call that carries no response timeout. The timer still fires once per due time, a tick
during its handler still does nothing, and a handler stopped with its silo still fires again on the next one.
- **A failing timer is logged.** A durable timer whose handler threw — or whose owner check or unregistration
failed — was visible only as Orleans' reminder error line. It is now logged as `117_137` `TimerFiringFailed` (Error)
with the owner, the purpose and the exception, and the timer fires again after its retry period as before.