Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>After digging through the various candidate solutions (use of <a href="http://msdn.microsoft.com/en-us/library/bb522489.aspx" rel="nofollow">Change Data Capture</a>, adapters for <a href="http://msdn.microsoft.com/en-us/library/ms345108%28v=sql.90%29.aspx" rel="nofollow">SQL Server Service Broker</a>, and possible conversions from <a href="http://en.wikipedia.org/wiki/Microsoft_Message_Queuing" rel="nofollow">MSMQ</a> to RabbitMQ), I came to a solution that should work for you.</p> <p>It turns out you can bind <a href="http://msdn.microsoft.com/en-us/netframework/aa663324" rel="nofollow">WCF</a> clients and service contracts to SQL Server. From here, you can use <a href="http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v1.5.1/rabbitmq-dotnet-client-1.5.1-wcf-service-model.pdf" rel="nofollow">RabbitMQ's AMQP binding for WCF</a> to translate messages back and forth, as the aforelinked PDF documents in great detail.</p> <p>I'm unclear on whether an additional transaction manager like XA will be required here, but if you suffer problems with transaction duplication, loops, and mismessaging, it's worth investigating as an intermediary for the connection. If you go that route, you'd need to weld that into your gateway in the same way you've defined in the problem statement. If this needs clarification, I'd be happy to expand on this here.</p> <p>Best of luck with your application. It sounds like an integration hydra from the outside, but once you get everything talking together, it should work nicely.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload