-
-
Notifications
You must be signed in to change notification settings - Fork 361
MSMQ transport
Linda Lawton edited this page Oct 10, 2017
·
4 revisions
Since MSMQ has no readily available mechanism for transferring raw key/value pairs, the Extension property (described here is used to transfer the bytes of a UTF7-encoded JSON serialized dictionary containing the Rebus headers.
-
rebus-express: Will be used to disable MSMQ dead-lettering (i.e. that the message ends up in the dead-letter queue when it expired or is deleted) and disable "recovery" (i.e. the message is not written to disk and therefore is not durable) -
rebus-time-to-be-received: The value will be interpreted as a time span ("HH:mm:ss") which is the "time-to-live" of the message. The message will be automatically removed from the queue when the TTL expires.
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