handle backpressure
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 218
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
How to solve [backpressure](https://www.reactivemanifesto.org/glossary#Back-Pressure) with Sieppari. Related:
* http://aleph.io/manifold/rationale.html
* https://funcool.github.io/catacumba/latest/#asynchronous
* https://github.com/pedestal/pedestal/issues/497
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
No source file or test is named. Start by reading the Reactive Manifesto definition and the linked Manifold, Catacumba, and Pedestal discussions, then identify Sieppari’s asynchronous interception entry points. Done should be a decided, project-specific approach to backpressure with its scope and expected behavior documented or tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100