-
-
Notifications
You must be signed in to change notification settings - Fork 364
Rebus versions
For historical reasons, there's something called "Rebus 1" (which is NuGet package versions <= 0.84.0), and there's something called "Rebus 2" (which is NuGet package versions >= 0.90.0).
"Rebus 1" and "Rebus 2" are NOT wire-compatible. "Rebus 2" is wire-compatible with all subsequent versions though, so if you're using NuGet package version 5, your endpoint can also communicate with endpoints of versions 4, 3, and 2(*).
Here's a table that gives an overview of the version history so far.
NuGet package version | Comment | Release date |
---|---|---|
0.9.1-alpha | First version | 2012-02-25 |
... | ||
0.16.0 | First non-pre | 2012-08-20 |
... | ||
0.84.0 | Last Rebus 1 | 2015-05-15 |
0.90.0 | First Rebus 2 | 2015-07-29 |
... | ||
2.0.1 | 2016-09-20 | |
... | ||
3.0.0 | 2017-01-04 | |
... | ||
4.0.0 | 2017-08-15 | |
... | ||
5.0.0 | 2018-10-08 | |
... | ||
6.0.0 | 2020-01-31 | |
... |
Check out Rebus on NuGet.org for information about the most recently released versions.
The changelog has information about which features/changes were made in each version.
(*) There's a caveat to this rule though: While all Rebus 2 versions use the same wire-level format (which is mostly about how message headers are used), each particular TRANSPORT might still impose some breaking changes. Most of them don't, but e.g. the SQL Transport has seen a breaking change from version 4 to 5, because it went from a single-table layout to a table-per-queue layout.
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