Skip to content

Add notices on Dead-Letter Queue support for Sagas #294

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 8, 2022
Merged

Add notices on Dead-Letter Queue support for Sagas #294

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions axon-framework/events/event-processors/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -277,6 +277,15 @@ To that end, the supported dead-letter queue is a so-called `SequencedDeadLetter
Integral to its design is to allow for queueing failed events and events that belong to a faulty sequence.
It does so by maintaining a sequence identifier for each event, determined by the [sequencing policy](/axon-framework/events/event-processors/streaming.md#sequential-processing).

> **Is there support for Sagas?**
>
> Currently, there is *no* support for using a dead-letter queue for [sagas](/axon-framework/sagas/README.md).
> We've taken this decision as we cannot support a sequenced dead lettering approach as we do for regular event handling.
>
> Furthermore, we cannot do this, as a saga's associations can vary widely between events.
> Due to this, the sequence of events may change, breaking this level of support.
> Hence, there's no way of knowing whether a next event in the stream does or does not belong to a saga.

Note that you *cannot* share a dead-letter queue between different processing groups.
Hence, each processing group you want to enable this behavior for should receive a unique dead-letter queue instance.

Expand Down