aws / aws/aws-dotnet-messaging

Immediate Dead letter option

Open
#165 1 comment 3 reactions 0 assignees View on GitHub
feature-request p2 queued
Dominant language
C#
Stars
143
Forks
27
Avg merge
1d 18h
Merged PRs (30d)
4

Description

### Describe the feature

A way of failing and immediately putting message to configured deadletter queue

### Use Case

if in handler code we are able to work out that no amount of retrying will resolve the issue without intervention there is no point wasting the processing retrying the message.

### Proposed Solution

some syntactic sugar such as ` return MessageProcessStatus.ImmediatelyDeadletter();`

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### AWS.Messaging (or related) package versions

AWS.Messaging 0.9.2

### Targeted .NET Platform

net8.0

### Operating System and version

AmazonLinux

Contributor guide

Open the contributing guide

Research direction

Start by tracing the message handler flow, retry behavior, and configured dead-letter queue around the proposed MessageProcessStatus.ImmediatelyDeadletter() result. Clarify how this status should differ from ordinary failures and define done as immediate placement of the message on the configured dead-letter queue without further retries.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, csharp
Domain
backend, cloud, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.