Skip to content
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.

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

[FEATURE REQUEST] Add redis stream support #475

Closed
aadog opened this issue May 22, 2022 · 2 comments
Closed

[FEATURE REQUEST] Add redis stream support #475

aadog opened this issue May 22, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@aadog
Copy link

aadog commented May 22, 2022

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@aadog aadog added the enhancement New feature or request label May 22, 2022
@hibiken
Copy link
Owner

hibiken commented Jun 4, 2022

Could you explain the motivation behind this feature request? Example use case would be very helpful to understand the motivation.

@hibiken hibiken closed this as completed Jun 26, 2022
@gebv
Copy link

gebv commented Dec 28, 2022

I thing redis stream helpfull for simpler mechanism for organizing workers?

  • ack
  • group consumer
  • xpending\xclaim If the worker (consumer) to finally fail

And is ideal for creating message brokers, message queues

And more HA

  • redis stream asynchronously replicates to slave nodes

let me know if you need more examples for asynq @hibiken

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants