Retries with backoff and a dead-letter state

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, postgresql

Research direction

Start by reading the repository’s outbox message sending and key ordering flow; the issue does not name files or tests. Identify where retry scheduling and message state are handled, then check how configurable limits are exposed. Done means repeated send failures wait progressively longer, and a message reaching the configured maximum is parked so it no longer blocks its key.

Written by the indexing model from the issue text.

Description

area: dispatch enhancement

A message whose send keeps failing waits longer each attempt and is parked after a configurable maximum, so it stops blocking its key.

Dominant language
C#
Stars
0
Forks
0
Avg merge
3m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from softvasco/outbox-kit

All issues in softvasco/outbox-kit

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.