-
-
Notifications
You must be signed in to change notification settings - Fork 362
Timeout Manager
mookid8000 edited this page Jan 21, 2013
·
5 revisions
Rebus' timeout manager is a vital part of a Rebus installation if you want to handle timeouts with a dedicated service.
Rebus can persist timeouts locally as well, but the central timeout manager has the benefit that it is in another process as your Rebus service, and therefore will not crash with your Rebus service (if it crashes), is not temporally coupled to your Rebus service, etc.
TODO: write some stuff about the timeout manager
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