-
-
Notifications
You must be signed in to change notification settings - Fork 364
Idempotence
Mogens Heller Grabe edited this page May 24, 2017
·
5 revisions
Idempotence (which you may read a formal definition of on Wikipedia), when we are talking about messaging, is when a message re-delivery can be handled without ending up in an unintended state.
Since we always run the risk of processing the same message twice, it is a good idea to think a little bit about idempotence from time to time.
Please read the page about delivery guarantees if it is not clear at this point why we might process the same message twice.
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