Connector for Azure Service Bus

The Solace PubSub+ Connector for Azure Service Bus bridges data between a PubSub+ event broker and an Azure Service Bus broker . The Connector for Azure Service Bus provides you (as an operator) a flexible and efficient way to integrate Azure Service Bus application data with your Solace-backed, event-driven architecture and the event mesh. The connector is deployable standalone or in redundancy modes of “active-standby” or “active-active” to allow for high-availability and horizontal scaling of your data movement. Each instance of this connector supports up to 20 individual, concurrent workflows (source-to-target pipeline), minimizing the number of connector instances deployed and managed.

Azure Service Bus offers different service tiers, each with varying capabilities. We've tested the Premium tier with this connector and it meets the expected performance throughput. In addition, even though the Azure Service Bus offers large message sizes of 80 MB and above, you cannot use message sizes larger than:

  • 30 MB for Solace PubSub+ Appliances, PubSub+ Software Event Brokers (Solace PubSub+ Enterprise Edition), or PubSub+ Event Broker Services (Enterprise service classes)
  • 10 MB for PubSub+ Software Event Brokers (Solace PubSub+ Standard Edition) or PubSub+ Event Broker Services (Developerservice class).

Ensure that you select an Azure Service Bus tier that meets your requirements for performance throughput. For more information about tier differences, see Azure Service Bus Premium messaging and Azure Service Bus Quotas.

Spring Framework technologies make it easy to configure the connector, perform advanced logging capabilities, and export live metric data to external monitoring solutions.

To get started deploying a connector locally or within a container, see:

For common configuration details, see:

For configuration settings that are specific to Azure Service Bus, see: