-
-
Notifications
You must be signed in to change notification settings - Fork 373
RabbitMQ transport
Mogens Heller Grabe edited this page Jul 11, 2019
·
4 revisions
RabbitMQ has native support for topic-based messaging, and Rebus will use that capability to implement pub/sub.
Therefore, the following configuration is enough for two Rebus instances to be able to communicate:
var subscriber = Configure.With(...)
.Transport(t = t.UseRabbitMq(connectionString, "my-subscriber"))
.Start();
var publisher = Configure.With(...)
.Transport(t = t.UseRabbitMq(connectionString, "my-publisher"))
.Start();after which you may go
await subscriber.Subscribe<MyEvent>();and then the subscriber will be subscribed to everything the publisher publishes like so:
await publisher.Publish(new MyEvent(...));Basic stuff
- Home
- Introduction
- Getting started
- Different bus modes
- How does rebus compare to other .net service buses?
- 3rd party extensions
- Rebus versions
Configuration
Scenarios
Areas
- Logging
- Routing
- Serialization
- Pub sub messaging
- Process managers
- Message context
- Data bus
- Correlation ids
- Container adapters
- Automatic retries and error handling
- Message dispatch
- Thread safety and instance policies
- Timeouts
- Timeout manager
- Transactions
- Delivery guarantees
- Idempotence
- Unit of work
- Workers and parallelism
- Wire level format of messages
- Handler pipeline
- Polymorphic message dispatch
- Persistence ignorance
- Saga parallelism
- Transport message forwarding
- Testing
- Outbox
- Startup/shutdown
Transports (not a full list)
Customization
- Extensibility
- Auto flowing user context extensibility example
- Back off strategy
- Message compression and encryption
- Fail fast on certain exception types
Pipelines
- Log message pipelines
- Incoming messages pipeline
- Incoming step context
- Outgoing messages pipeline
- Outgoing step context
Prominent application services