-
-
Notifications
You must be signed in to change notification settings - Fork 363
How does rebus compare to other .net service buses?
The most prominent .NET service bus implementation out there, and the one that inspired me to create Rebus. I like almost everything about the messaging parts of NServiceBus, but I'd say that NServiceBus is very much a framework, whereas the Rebus philosophy is to stay small and library-like.
This means that NServiceBus can probably do everything that Rebus can do, and in addition to that it can install MSMQ for you, manage environment configurations, install performance counters, host your bus, and probably one million other things.
One core difference between Rebus and NServiceBus, is that Rebus does not default to using DTC and distributed transactions. If you're curious, you can read more about Rebus' transactions.
The most prominent free .NET service bus implementation out there, and one that I had such a hard time configuring and running in 2010 that I gave up and created Rebus.
I don't know that much about MassTransit, except it seems that RabbitMQ has become the de facto default transport for it. If anyone knows more about this, please enlighten me :)
Please tell me about them :)
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