Stratara.Outbox.AzureServiceBus
3.1.1
See the version list below for details.
dotnet add package Stratara.Outbox.AzureServiceBus --version 3.1.1
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 3.1.1
<PackageReference Include="Stratara.Outbox.AzureServiceBus" Version="3.1.1" />
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="3.1.1" />
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
paket add Stratara.Outbox.AzureServiceBus --version 3.1.1
#r "nuget: Stratara.Outbox.AzureServiceBus, 3.1.1"
#:package Stratara.Outbox.AzureServiceBus@3.1.1
#addin nuget:?package=Stratara.Outbox.AzureServiceBus&version=3.1.1
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=3.1.1
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.1)
- Stratara.Shared (>= 3.1.1)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
### Fixed
- **`FileMasterKeyProvider` now rejects a master KEK that is not exactly 32 bytes at startup.**
The KEK is used directly as an AES-256-GCM key, which accepts only 16/24/32-byte keys. The
provider previously required merely *at least* 32 bytes, so a longer KEK (for example the
48-byte output of `openssl rand -base64 48`, a common HKDF master-key recipe) passed both
construction and the eager `FileKeyStoreStartupProbe`, then threw
`CryptographicException: Specified key is not a valid size for this algorithm` on the **first**
key creation at runtime — defeating the purpose of the boot-time probe. The provider now
validates the decoded length is exactly 32 bytes and fails fast at boot with an actionable
message (`Generate one with: openssl rand -base64 32`). A 32-byte KEK is unaffected.
- **`EnvelopeFileKeyStore` is now safe for multiple processes sharing one store file** (for
example several containers bind-mounting the same host directory). Previously a process only
read the store once at construction, so a data-encryption key created by another process after
startup was invisible (`GetDataEncryptionKeyAsync` returned `null`, breaking decryption), and
two processes creating keys concurrently could overwrite each other's keys or mint colliding
versions for the same scope. Reads now reload from disk on a cache miss (guarded by the file's
last-write time to avoid reload storms), and every mutation serializes through an exclusive
cross-process lock file and re-reads the latest on-disk state before writing. A networked file
system (NFS/SMB) remains unsupported — it guarantees neither atomic rename nor reliable advisory
locks.
### Added
- **`LogEvents.KeyManagement.KeyStoreReloaded` (112_006)** — debug-level event emitted when the
file key store reloads its state from disk to pick up keys written by another process.