You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an optional functionality for inter-topic dependency management, to resolve the following issues:
If an Event 1 for entity A fails in a topic and is sent to the non-blocking retry or dead letter queue, it may be desired that Event 2 for the same entity A should also not be processed until Event 1 succeeds (Event 2 should be put in a holding queue). Essentially, the order of events for the same entity needs to be respected.
It could be that messages in some topics should not be processed before messages in other topics. These dependent messages should be put in a holding queue until their dependency in the other topic has been processed.
"Entity" can be determined by the message key normally, but ideally it should be overideable.
Add an optional functionality for inter-topic dependency management, to resolve the following issues:
"Entity" can be determined by the message key normally, but ideally it should be overideable.
Sources for implementation:
The text was updated successfully, but these errors were encountered: