All geek questions in one place

Best Alternative to MSMQ Transport in NServiceBus

We regularly get problems with MSMQ in Nsb, because at some point MSMQ on one computer does not want to receive messages from another machine until we restart the service or restart the computer. Therefore, we are looking for alternatives. However, we would like to keep these important MSMQ features:

  • part of distributed transactions so that subsequent messages are not sent from the Nsb handler if the handler rolls back the transaction. We use MSDTC;
  • Incoming or outgoing messages should be stored in reliable, persistent storage, such as a disk or database, if the Nsb service receiver is not available and no message should be lost.
  • It can handle a huge volume of messages, currently we process as thousands of messages every second for all services combined or it can be one hundred or two per second per service

Here is a list of alternative Nsb sources: https://docs.particular.net/transports/

Does anyone have any experience with any of this?

+4
source share
1 answer

I personally would try to solve my problems with MSMQ and make the system work fine, many systems work in MSMQ ... However, if you decide to switch, I think that the best alternative, given your capabilities above, is the SQL transport server

+3
source

Source: https://habr.com/ru/post/1682446/

More articles:


All Articles