Hi everyone,
We’ve just released NServiceBus.Transport.AzureServiceBus 5.0.0.
This version introduces a new topic-per-event topology that dedicates one Azure Service Bus topic to each concrete event type. This approach can dramatically reduce filtering overhead and improve both performance and scalability by distributing messages across multiple topics, each dedicated to a single event type.
For a more phased migration from the default single-topic approach in previous versions, this release also introduces a migration topology. This topology lets endpoints continue using the existing single-topic event routing approach while selectively shifting certain events to the new topic-per-event model.
This release is a major upgrade from version 4. If you’re moving from v4 (or any earlier version), careful planning is required to avoid disruptions. Please refer to the NServiceBus.Transport.AzureServiceBus version 4 to 5 upgrade guide for detailed migration steps and the topology documentation, including:
- How to gradually migrate existing endpoints and events with the migration topology.
- Quotas, subscription limits, and advanced considerations such as interface-based inheritance and message versioning.
We strongly recommend reading the upgrade guide in full before beginning the process.
Please share any challenges you faced or rough edges you discovered during the migration on this discussion group entry or GitHub issue. We’re actively monitoring both. If discussing specifics about your project is necessary, feel free to raise a support request. We can provide the help you need to migrate from any earlier version to the latest release.
When to upgrade
This upgrade significantly improves transport functionality. We recommend preparing early, planning the upgrade carefully, and considering the order of endpoints and events—but don’t wait until the last moment.
Where to get it
You can install NServiceBus.Transport.AzureServiceBus 5.0.0 from NuGet.
With thanks,
The team in Particular
Please read our release policy for more details.