-
-
Notifications
You must be signed in to change notification settings - Fork 361
Outgoing messages pipeline
Mogens Heller Grabe edited this page Jun 22, 2016
·
2 revisions
When sending outgoing messages, the message gets passed through the outgoing pipeline - no matter if the message is sent with Send, SendLocal, Reply, etc.
Rebus will add the sent message to a new outgoing step context and then invoke its pipeline of outgoing message steps.
See the log message pipelines page for information on how to get to see what the pipeline contain.
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