Stratara.Outbox.AzureServiceBus
3.1.5
See the version list below for details.
dotnet add package Stratara.Outbox.AzureServiceBus --version 3.1.5
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 3.1.5
<PackageReference Include="Stratara.Outbox.AzureServiceBus" Version="3.1.5" />
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="3.1.5" />
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
paket add Stratara.Outbox.AzureServiceBus --version 3.1.5
#r "nuget: Stratara.Outbox.AzureServiceBus, 3.1.5"
#:package Stratara.Outbox.AzureServiceBus@3.1.5
#addin nuget:?package=Stratara.Outbox.AzureServiceBus&version=3.1.5
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=3.1.5
Stratara.Outbox.AzureServiceBus
License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.
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:
builder.Services.AddSingleton<ServiceBusClient>(_ =>
new ServiceBusClient(builder.Configuration.GetConnectionString("ServiceBus")!));
builder.Services.AddSingleton<IMessageBus, AzureServiceBusBus>();
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.1.5)
- Stratara.Shared (>= 3.1.5)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Added
- **Configurable snapshot strategy** (`Stratara.Abstractions`, `Stratara.Infrastructure`) — the
snapshot cadence is no longer hard-coded. A new `Stratara.Abstractions.EventSourcing.ISnapshotStrategy`
decides, per stream, whether the event-sourcing runtime should write a snapshot:
`bool ShouldSnapshot(Type aggregateType, long currentVersion, long lastSnapshotVersion)`.
`AddEventSourcing()` registers the default `VersionThresholdSnapshotStrategy` (snapshot every 50
versions — identical to the previous behaviour) via `TryAddSingleton`, so existing consumers see no
change. To take over the policy, register your own singleton `ISnapshotStrategy` (it overrides the
default whether registered before or after `AddEventSourcing()`): vary the threshold per aggregate
type, construct `new VersionThresholdSnapshotStrategy(threshold)` for a different uniform cadence, or
register `NoSnapshotStrategy` to disable snapshotting entirely. This replaces the previously
hard-coded `UseSnapshots`/`SnapshotRange` constants in the default snapshot service, which were not
actually configurable despite the documentation implying they were.
- **`AddDomainEventTypesFromAssemblyContaining<T>()`** (`Stratara.Abstractions`) — registers *only* the
domain event types consumed by an assembly's aggregate `Apply(TEvent)` methods in the trusted-type
resolver, without registering the aggregate types themselves and without pulling any projection / saga
/ command-handler classes into DI. Use it in a host that only needs to deserialize event payloads off
the message bus or event stream — typically a dedicated projection or saga worker — but must not wire
the handler classes (and their runtime dependencies) that `AddProjectionsFromAssemblyContaining<T>`
would register. Complements the existing `AddAggregatesFromAssemblyContaining<T>` (which additionally
registers the aggregate types) and `AddTrustedType<T>` (single type).