-
-
Notifications
You must be signed in to change notification settings - Fork 366
Return to source queue tool
Mogens Heller Grabe edited this page Jan 4, 2020
·
4 revisions
unfortunately does not exist for recent versions of Rebus.
At the moment, the best generally applicable solution is to subscribe to Rebus Pro, because that will give you access to Fleet Manager.
When Fleet Manager is used, dead-letter queues are no longer used: Failed messages will be stored in Fleet Manager's database, and messages can be re-delivered (to the source queue, or any other queue) by the click of a button.
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