eventservice: avoid blocking EventStore notifications when the scan queue is full
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
Currently, EventStore notifications may be blocked when the EventService scan queue is full, which can delay progress updates for other dispatchers.
We should introduce an asynchronous preparation stage between EventStore notifications and scan workers. Notifications should return promptly, while repeated scan requests are combined and scheduled internally with proper backpressure.
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
Trace the EventStore notification path into the EventService scan queue and scan workers; the issue names these components but no files or tests. Verify how a full queue currently blocks notifications, then define completion as prompt notification returns, coalesced repeated scan requests, and internal scheduling with backpressure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100