Micro-Integration for Azure Service Bus

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

Azure Service Bus offers different service tiers, each with varying capabilities. We've tested the Premium tier with this Micro-Integration 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 Appliance Event Brokers, Solace Software Event Brokers (Solace Enterprise Edition), or Solace Event Broker Services (Enterprise service classes)
  • 10 MB for Solace Software Event Brokers (Solace Standard Edition) or Solace Event Broker Services (Enterprise-100 Standaloneservice 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 Micro-Integration, perform advanced logging capabilities, and export live metric data to external monitoring solutions.

To get started deploying a Micro-Integration locally or within a container, see:

For common configuration details, see:

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