poison message
A message that fails every time it is processed, for example because it is malformed, and would block a queue if retried forever.
In more detail
A dead letter queue catches it after a limited number of attempts. Record why it failed so someone can fix the data or the code and replay it.
Example
In Kafka an uncaught error on one bad record stops the whole partition.Related terms
- dead letter queue — A separate queue where messages that keep failing are moved, so they stop blocking others and can be inspected and replayed later.
- message queue — A store that holds messages from producers until consumers are ready to process them, decoupling the rate of arrival from the rate of work.
- exception — An error object a program raises to stop normal flow and report that something went wrong.
- ordering guarantee — A promise about whether messages are processed in the order they were sent, which is often limited to one key or partition.
Taught in
- Event-Driven Architecture And Queues — Modern API Architecture: REST, GraphQL & gRPC
- Stuck On One Record — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Night Before The Administrator Exam — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Poison Messages And Dead Letter Topics — Apache Kafka & Event Streaming
- Retries With Backoff Topics — Apache Kafka & Event Streaming
- Queues, Events And Asynchronous Work — Scalable System Design & Distributed Architecture