Azure Service Bus Transport Upgrade Version 7 to 8

Forwarding Topology number of entities in bundle removed

In Versions 8 and above the API to configure bundle prefix and number of entities in a bundle has been removed:

7.x - 7.2.3 NServiceBus.Azure.Transports.WindowsAzureServiceBus
var transport = endpointConfiguration.UseTransport<AzureServiceBusTransport>();
var forwardingTopology = transport.UseForwardingTopology();

forwardingTopology.BundlePrefix("my-prefix");
forwardingTopology.NumberOfEntitiesInBundle(3);

The bundle is set to one entity. For existing endpoints running with multiple entities in a bundle, the transport automatically picks up previously configured entities. The default topic name for bundle is set to bundle-1.

See also Azure Service Bus Transport Topologies.

Controlling entity creation

Controlling entity creation has been simplified. Instead of having to provide a full implementation of DescriptionFactory where all settings on the description object had to be provided, a customizer (DescriptionCustomizer) has been introduced where only the customized properties can be changed. DescriptionCustomizer can be found on the Queues, Topics and Subscriptions API extension points.

BrokeredMessage conventions

Due to complexity, and resultant risk, of implementation, the API to specify how the BrokeredMessage body is stored and retrieved by overriding the default conventions is obsoleted and the following methods were deprecated:

7.x NServiceBus.Azure.Transports.WindowsAzureServiceBus
var transport = endpointConfiguration.UseTransport<AzureServiceBusTransport>();
transport.UseBrokeredMessageToIncomingMessageConverter<CustomIncomingMessageConversion>();
7.x NServiceBus.Azure.Transports.WindowsAzureServiceBus
var transport = endpointConfiguration.UseTransport<AzureServiceBusTransport>();
transport.UseOutgoingMessageToBrokeredMessageConverter<CustomOutgoingMessageConversion>();

Related Articles


Last modified