The transport is not compatible with RabbitMQ broker Versions 3.3.X and below.
To use RabbitMQ as the underlying transport:
The RabbitMQ transport requires a connection string to connect to the broker. See Connection settings for options on how to provide the connection string.
- RabbitMQ provides native reliability and high-availability features.
- Offers native Publish-Subscribe mechanism, therefore it doesn't require NServiceBus persistence for storing event subscriptions.
- Wide range of supported clients allows for integrating the system with applications written in other languages using native RabbitMQ features.
- Supports Competing consumers pattern out of the box. Messages are received by instances in a round-robin fashion without additional configuration.
- Doesn't handle network partitions well, partitioning across a WAN requires using dedicated features.
- Requires careful consideration with regards to duplicate messages, e.g. using the Outbox feature or making all endpoints idempotent.
- Many organizations don't have the same level of expertise with RabbitMQ, as for example with SQL Server, so it may require additional training.
- Might require covering additional costs of commercial RabbitMQ license and support.