-
-
Notifications
You must be signed in to change notification settings - Fork 364
Manual configuration
Mogens Heller Grabe edited this page Aug 26, 2015
·
5 revisions
Manually configuring Rebus is easy, but it requires that you have a fair amount of knowledge about how Rebus (and the NServiceBus/MassTransit/Rhino ESB class of service bus implementations in general) achieve their functionality.
You do it like this:
var bus = new RebusBus(...);
and then you
bus.Start();
Of course the constructor above is not satisfied with ...
, it does require some real stuff to be passed to it, which is listed and described below:
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