Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat] Add Dead-Letter Queue (DLQ) for Failures #139

Open
yordis opened this issue Sep 26, 2022 · 4 comments
Open

[Feat] Add Dead-Letter Queue (DLQ) for Failures #139

yordis opened this issue Sep 26, 2022 · 4 comments
Labels

Comments

@yordis
Copy link
Contributor

yordis commented Sep 26, 2022

Related to #138

Along with acking the message to avoid queueing the system on a failure, it is also prudent that we must publish successfully into a DLQ topic the failed message.

Acceptence Criteria

As an operator:

  • I would allow to configure a DLQ topic name where the failed messages will be published to

As an application dev:

  • I expect a DLQ message to be published when a message is processed.
@adamdecaf
Copy link
Member

This seems like a handy feature. Would you like to work on it?

@adamdecaf
Copy link
Member

I'm assuming failures encountered by #136 would appear on this DLQ, right?

@yordis
Copy link
Contributor Author

yordis commented Sep 28, 2022

Yes, everything that could be "missed" in the processing would be a DLQ for late consumption of the message.

Being said,

You could also split the DLQ into broken message structures and have a failures topic for those things.

I instead do the latter architecturally.

@yordis
Copy link
Contributor Author

yordis commented Sep 28, 2022

This seems like a handy feature. Would you like to work on it?

I will as soon as I have some time, this will be critical to us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants