Stratara.Outbox.AzureServiceBus
3.2.1
Prefix Reserved
See the version list below for details.
dotnet add package Stratara.Outbox.AzureServiceBus --version 3.2.1
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 3.2.1
<PackageReference Include="Stratara.Outbox.AzureServiceBus" Version="3.2.1" />
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="3.2.1" />
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
paket add Stratara.Outbox.AzureServiceBus --version 3.2.1
#r "nuget: Stratara.Outbox.AzureServiceBus, 3.2.1"
#:package Stratara.Outbox.AzureServiceBus@3.2.1
#addin nuget:?package=Stratara.Outbox.AzureServiceBus&version=3.2.1
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=3.2.1
Stratara.Outbox.AzureServiceBus
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→AbandonMessageAsync(Service Bus redelivers)- any other exception →
DeadLetterMessageAsync(explicit DLQ with the exception type as reason)
System-level errors (connection drops, auth failures) arrive via ProcessErrorAsync and are logged; the Service Bus client owns the reconnect / retry policy for those.
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.20.1)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.8)
- Microsoft.Extensions.Options (>= 10.0.8)
- Stratara.Abstractions (>= 3.2.1)
- Stratara.Shared (>= 3.2.1)
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.2.0 | 61 | 9/18/2026 |
| 4.1.1 | 85 | 9/16/2026 |
| 4.1.0 | 82 | 9/16/2026 |
| 4.0.4 | 95 | 9/14/2026 |
| 4.0.3 | 94 | 9/3/2026 |
| 4.0.2 | 101 | 9/3/2026 |
| 4.0.1 | 94 | 9/2/2026 |
| 4.0.0 | 95 | 8/31/2026 |
| 4.0.0-preview.1 | 65 | 8/31/2026 |
| 3.4.0 | 97 | 8/28/2026 |
| 3.3.0 | 98 | 8/25/2026 |
| 3.2.3 | 100 | 8/22/2026 |
| 3.2.2 | 105 | 8/14/2026 |
| 3.2.1 | 116 | 8/2/2026 |
| 3.2.0 | 112 | 7/18/2026 |
| 3.1.7 | 225 | 7/1/2026 |
| 3.1.6 | 122 | 6/22/2026 |
| 3.1.5 | 122 | 6/22/2026 |
| 3.1.4 | 118 | 6/15/2026 |
| 3.1.3 | 127 | 6/10/2026 |
### Fixed
- **Snapshot loads are now scoped to the aggregate type.** The snapshot read previously filtered
only by stream id, so when two aggregate types shared a stream id, rehydrating one type could
pick up the other type's (higher-versioned) snapshot and deserialize it into the requested type —
silently returning an aggregate with default/empty fields. Snapshot reads now match the aggregate
type (version-independently, so an assembly rev-bump does not invalidate existing snapshots), and
snapshot writes are grouped per `(stream, aggregate type)` so a stream carrying more than one type
snapshots each type independently. A snapshot of type X may now only ever rehydrate type X.
### Changed
- **`ISnapshotRepository` gained type-scoped read overloads.** `GetAsync(streamId,
aggregateTypeName, toVersion, ct)` and `GetLatestVersionOrDefaultAsync(streamId,
aggregateTypeName, ct)` are the correct lookups; the previous type-less overloads are now
`[Obsolete]` because they can return a foreign aggregate type's snapshot on a shared stream.
Custom `ISnapshotRepository` implementers should add the new overloads.