openworkflowdev / openworkflowdev/openworkflow
enable workers to poll only to specific workflow tasks
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 66
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 69
Description
Is your feature request related to a problem? Please describe.
I am planning to have workers processes to register specific workflows based on service configuration (e.g. environment variables).
This would allow configuring pools of workers dedicated to specific workflows
For example:
- one worker pool could be dedicated to a single critical workflow with high throughput and long running steps
- another worker pool could handle the remaining, less frequent and not so critical, short workflows
Describe the solution you'd like
By default the worker should only poll workflows from the backend that match the task names defined on the instance.
Describe alternatives you've considered
The namespaceId could be abused for this, but it would not feel right and is very limited.
Additional context
none
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or concrete entry points are identified in the issue. Start by locating the worker polling and instance-configuration entry points, then trace how task names reach backend polling. Done means configured workers poll only matching workflow tasks while the default behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100