feat - flow control & concurrency / parallelism limits
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 365
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 169
Description
I would like the ability to add rate limits & concurrency/parallelism limits (aka flow control) config on my different workflows / steps. Qstash has similar feature see here (https://upstash.com/docs/qstash/features/flowcontrol)
I can see how to implement this in the local world, postgres & redis worlds.
however I don't see a clear path right now to implementing this in the vercel world with vercel queues.
if this cannot currently be implemented with vercel queues, is that a blocker to the feature being added at all?
It would be optional config so non-breaking, and the different worlds could then implement this later.
If this could still be added I would work on opening a PR for it for local + postgres.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the workflow and step configuration entry points, then compare how flow control could work in the local and PostgreSQL worlds with the constraints of Vercel Queues. Done means optional rate and concurrency/parallelism limits are defined for workflows or steps, with a clear decision on Vercel-world support and coverage for the supported implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100