none
MSMQ vs Service broker RRS feed

  • Question

  • Hi friends,

    My existing project does db operation with help of MSMQ.

    Consider following steps ;

    1.Main Application writes binary dataa to MSMQ
    2.Sub application reads data from MSMQ and update DB.

    I have tried this with service broker

    1.Main applicate puts data into Database Queue through Service broker
    2.Service broker does DB operation.

    But Comparatively the performance in service broker is very very slow.

    I have used Binary data which passes through Queue and i have used CLR enabled stored procedure to use this bianry data.

    Can any one explain wats wrong in this.Hi friends,




    Monday, June 2, 2008 12:06 PM

Answers

  • MSMQ is a message transport and not a database so if application messages themselves are important business objects that must have high data integrity including backup and failover, Service Broker is also a better choice.  If your application can survive an occasional lost message, must communicate over HTTP, or can’t live with a SQL Server database at both ends of the communications link, then MSMQ is a better choice. 

     

    For more information, please visit http://blogs.msdn.com/rogerwolterblog/archive/2006/02/28/540803.aspx

    Thursday, June 5, 2008 7:46 AM

All replies

  • MSMQ is a message transport and not a database so if application messages themselves are important business objects that must have high data integrity including backup and failover, Service Broker is also a better choice.  If your application can survive an occasional lost message, must communicate over HTTP, or can’t live with a SQL Server database at both ends of the communications link, then MSMQ is a better choice. 

     

    For more information, please visit http://blogs.msdn.com/rogerwolterblog/archive/2006/02/28/540803.aspx

    Thursday, June 5, 2008 7:46 AM
  • Does my reply answered your question or anything else you want to  know?

    Thursday, June 12, 2008 5:39 AM