After searching for various candidate solutions (using Change Data Capture adapters for SQL Server Service Broker and possible conversions from MSMQ to RabbitMQ), I came up with a solution that should work for you.
Turns out you can bind WCF clients and service contracts to SQL Server. From here, you can use the RabbitMQ AMQP binding for WCF to translate messages back and forth, as PDF documents are described in detail.
I donβt understand if an additional transaction manager, such as XA, is needed here, but if you have problems with transaction duplication, cycles and errors, it is worth exploring as an intermediary for connection. If you are following this route, you need to weld it in your gateway in the same way as you identified in the statement of problem. If this requires clarification, I would be happy to expand it here.
Best of luck with your application. It sounds like an integral hydra from the side, but as soon as you get everything you say together, it should work well.
MrGomez
source share