Connector for Azure Service Bus

The Solace PubSub+ Connector for Azure Service Bus bridges data between the Solace PubSub+ event broker and an Azure Service Bus. 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 PubSub+ connector supports up to 20 individual, concurrent workflows (source-to-target pipeline), minimizing the number of connector instances deployed and managed.

The use of various Spring Framework technologies allows for easy configuration of the connector, advanced logging capabilities, and the export of live metric data to external monitoring solutions.

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

• Getting Started with the Connector for Azure Service Bus .
• Modifying the Container Configuration .

There are two major aspects to configure this connector:

• Configuring the datapath for the connector (or how data flows between PubSub+ and Azure Service Bus. For more information, see Configuring the Datapath for the Connector for Azure Service Bus.
• Specific connector deployment and management configuration, such as managing metrics or configuring redundancy. For more information, see Configuring the Management and Deployment of the Connector for Azure Service Bus.

Support

Community support (best effort) is offered from Solace Developer Community forums. For premium support options, contact Solace.