This is the same risk with any DLQ. The idea behind a DLQ is it will retry (with... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		with 3 days ago \| parent \| context \| favorite \| on: Using PostgreSQL as a Dead Letter Queue for Event-... This is the same risk with any DLQ. The idea behind a DLQ is it will retry (with some backoff) eventually, and if it fails enough, it will stay there. You need monitoring to observe the messages that can't escape DLQ. Ideally, nothing should ever stay in DLQ, and if it does, it's something that should be fixed.

microlatency 2 days ago [–]

What do you use for the monitoring of DLQs?

with 2 days ago | [–]

At my last workplace, we used pure AWS Cloudwatch. At my new workplace, we use Grafana+Sentry

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact