The Azure Service Bus transport leverages the Azure.Messaging.ServiceBus client library for .NET.
Azure Service Bus is a messaging service hosted on the Azure platform that allows for exchanging messages between various applications in a loosely coupled fashion. The service offers guaranteed message delivery and supports a range of standard protocols (e.g. REST, AMQP, WS*) and APIs such as native pub/sub, delayed delivery, and more.
Transport at a glance
| Feature | |
|---|---|
| Transactions | None, ReceiveOnly, SendsAtomicWithReceive |
| Pub/Sub | Native |
| Timeouts | Native |
| Large message bodies | with Premium tier or data bus |
| Scale-out | Competing consumer |
| Scripted Deployment | Supported using NServiceBus. |
| Installers | Optional |
| Native integration | Supported |
| Message sessions | Not supported |
| Case Sensitive | No |
| Aspire integration | Yes |
The Azure Service Bus transport only supports the Standard and Premium tiers of the Microsoft Azure Service Bus service. Premium tier is recommended for production environments.
Support for Azure Service Bus message sessions is being considered. If session-based ordered processing is required, add a thumbs-up or share the use case on issue #535.
Azure Service Bus Emulator
The Azure Service Bus transport works with the Azure Service Bus emulator. To use the emulator, your connection string must include UseDevelopmentEmulator=true;
Known Emulator Limitations
The emulator is only suitable for small systems, since it contains limitations on connections and queue size. For anything larger, a full Azure Service Bus instance will be required.
The current known limitations that affect functionality with the Particular Service Platform are:
- A limit of 10 connections. Each NServiceBus endpoint will use a connection for sending and a connection for receiving, effectively using 2 connections for a full endpoint.
MaxDeliveryCountis fixed at 10.