NServiceBus features requiring usage of Transport Adapter

Some features of NServiceBus, particularly related to physical routing of messages, cannot be supported by ServiceControl. The reason for not supporting them is the fact that these features require extensive code-based configuration and ServiceControl is a stand-alone service. The Transport Adapter is designed to bridge the gap. Transport Adapter is provided as a library package (rather than stand-alone service) so users can customize the transport the same way as they do for the regular business endpoints.

SQL Server transport

The multi-instance where endpoints connect to different instances of SQL Server is not supported because ServiceControl can't send a retried failed message to the endpoint's own database.

RabbitMQ transport

Neither direct topology nor custom topologies are supported as ServiceControl is configured to use the default topology which expects an exchange exists with the name same as the destination endpoint's name.

Azure Service Bus

Azure Storage Queues

Amazon SQS

The Amazon SQS transport is not supported by ServiceControl. In order to use ServiceControl with a system that uses Amazon SQS, the ServiceControl has to be configured to use one of the supported transports (e.g. MSMQ, SQL Server) and a transport adapter has to be deployed to translate from SQS to the ServiceControl transport.

Last modified