Add Redis Streams event queue provider #700
Open
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
Implement a new event queue provider using Redis Streams with the Lettuce client for reliable messaging with consumer groups. New module: redis-event-queue - RedisObservableQueue: Core implementation using XREADGROUP/XACK - RedisEventQueueProvider: Queue factory with caching - RedisEventQueueConfiguration: Spring Boot auto-configuration - Support for dead letter queue (DLQ) via separate stream Configuration prefix: conductor.event-queues.redis.*
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.
Implement a new event queue provider using Redis Streams with the Lettuce client for reliable messaging with consumer groups.
New module: redis-event-queue
Configuration prefix: conductor.event-queues.redis.*
Pull Request type
NOTE: Please remember to run
./gradlew spotlessApplyto fix any format violations.Changes in this PR
Describe the new behavior from this PR, and why it's needed
Issue #
Alternatives considered
I could not find a suitable alternative.