pubsub: Implement optional durable event delivery #637
+1,167
−16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nuclearcat
force-pushed
the
durable-pub-sub
branch
6 times, most recently
from
8dbfab1 to
ff82d6e
Compare
Major feature: removing "fire-and-forget" event delivery mode with Redis to allow durable event delivery over MongoDB. Unified storage: Events stored once in eventhistory (was duplicated) Auto-migration: Detects old 24h TTL format, drops and recreates Backwards compatible: Without subscriber_id = fire-and-forget (old behavior) Durable mode: With subscriber_id = catch-up on missed events Implicit ACK: Polling for next event acknowledges previous Signed-off-by: Denys Fedoryshchenko <[email protected]>
nuclearcat
force-pushed
the
durable-pub-sub
branch
2 times, most recently
from
825a90e to
90d433c
Compare
Signed-off-by: Denys Fedoryshchenko <[email protected]>
nuclearcat
force-pushed
the
durable-pub-sub
branch
from
90d433c to
8ebba65
Compare
Member
Author
|
tested on staging |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Major feature: removing "fire-and-forget" event delivery mode with Redis to allow durable event delivery over MongoDB.
Unified storage: Events stored once in eventhistory (was duplicated)
Auto-migration: Detects old 24h TTL format, drops and recreates
Backwards compatible: Without subscriber_id = fire-and-forget (old behavior)
Durable mode: With subscriber_id = catch-up on missed events
Implicit ACK: Polling for next event acknowledges previous