Azure Service Bus vs RabbitMQ for enterprise applications

Question

I need to decide between Azure Service Bus and RabbitMQ (Deployed on Azure) for an enterprise application, and my main use will consist of themes (with long-term storage). I see that the service bus has more features than RabbitMQ, such as retry count, TTL, sessions and transactions, etc. But I'm not sure which one is best for high availability, scalability, storage, and bandwidth. The service bus has some restrictions on the size of the store (max. 5 GB for an off-season queue and 80 GB for a partitioned queue) and throughput of 2000 ms / s / queue. What if I need more of these restrictions in the case of a service bus?

The limits of RabbitMQ are not clear, as it depends on the cluster. If someone can help me in deciding which one will be the best in my case?

Answer 1

However, your question was asked a long time ago, I see that people are still visiting. I found two useful sources:

(1) Here is an exhaustive (albeit old) article comparing Service Bus with RabbitMQ :

http://geekswithblogs.net/michaelstephenson/archive/2012/08/12/150399.aspx

Summary of the above ():

(2) Looking at this answer may also help a little:

https://dba.stackexchange.com/questions/196770/sql-server-service-broker-vs-rabbitmq

, , , :

• ? () → RMQ. () → SSB. , - ,      pub-sub SQLCLR.      ()      ( , ).

• SSB? SSB , , , . , SSB - () .

.