sassoftware / sassoftware/arke
research best rate for acking for streams
Open
Nobody has claimed this yet.
event-stream
research
- Dominant language
- Go
- Stars
- 6
- Forks
- 2
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 8
Description
Currently we store the offset for streams after every message. We should research a more appropriate rate. I recommend looking at using Prefetch.
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
Start by locating the stream offset persistence and acknowledgement entry points in the Go repository, then review how Prefetch could affect the current per-message behavior. Done means a documented recommendation for an acknowledgement rate and a clear implementation direction, with supporting observations or measurements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100