mirror of
https://github.com/hibiken/asynq.git
synced 2026-04-25 23:15:51 +03:00
[GH-ISSUE #421] Multiple handlers for a specific task type ? #2211
Labels
No labels
CLI
bug
designing
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
idea
invalid
investigate
needs-more-info
performance
pr-welcome
pull-request
question
wontfix
work in progress
work in progress
work-around-available
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/asynq#2211
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @raynaudoe on GitHub (Mar 18, 2022).
Original GitHub issue: https://github.com/hibiken/asynq/issues/421
Let's say that I have a task named
data:processand the payload contains some raw json for example and I want that task to be distributed to 'several' handlers, the task should be processed by 'all' the handlers.Something like:
is this possible ?
Thanks a lot
@hibiken commented on GitHub (Mar 18, 2022):
@raynaudoe thank you for the question!
Is this similar to this other question #410?
@raynaudoe commented on GitHub (Mar 19, 2022):
Thanks @hibiken , yeah, something like consumers groups.
The difference with the example on that issue is that, initially, my handlers (dataProcessorA, dataProcessorB ...) they all handle the same type of task but each processor analyzes let's say some aspect of the payload. Then the 'final' result is the sumatory of all the handler's outputs.
I'm sure that I can achieve the above using kafka or similar but since I'm using asynq for another component I thought I could achieve the same result without needing an extra package.
@hibiken commented on GitHub (Mar 20, 2022):
I see. It sounds like this use case may benefit from a workflow feature like this one (#244)? Essentially you'd create a set of tasks to handle multiple stages in your workflow.
I'm planning to work on this laster half of this year so the feature is coming :)
@raynaudoe commented on GitHub (Mar 21, 2022):
thanks! yeah, I really like the workflows idea! Looking forward to it :)