Dead letter queue
In message queueing the dead letter queue is a service implementation to store messages that meet one or more of the following criteria:
- Message that is sent to a queue that does not exist.[1][2]
- Queue length limit exceeded.
- Message length limit exceeded.
- Message is rejected by another queue exchange.[3]
- Message reaches a threshold read counter number, because it is not consumed. Sometimes this is called a "back out queue".
- The message expires due to per-message TTL (time to live)[4]
- Message is not processed successfully.
Dead letter queue storing of these messages allows developers to look for common patterns and potential software problems.[5]
Queueing systems that incorporate dead letter queues include ,[6] Amazon Simple Queue Service,[5] Apache ActiveMQ, Google Cloud Pub/Sub,[7] HornetQ, Microsoft Message Queuing,[1] Microsoft Azure Event Grid and Azure Service Bus,[8] WebSphere MQ,[9] ,[10] Rabbit MQ,[3] Apache Kafka[11] and .[12][13]
See also[]
References[]
- ^ a b Redkar, Arohi (2004). Pro MSMQ: Microsoft Message Queue Programming. Apress. p. 148. ISBN 1430207329.
- ^ "Dead-letter queues". IBM. Retrieved 23 February 2014.
- ^ a b RabbitMQ dead letter queue "Dead Letter Exchanges".
- ^ "Dead Letter Exchanges — RabbitMQ". www.rabbitmq.com. Retrieved 2020-12-06.
- ^ a b "Using Amazon SQS Dead Letter Queues". Amazon. Retrieved 23 February 2014.
- ^ "Amazon EventBridge announces support for Dead Letter Queues". Amazon.
- ^ "Forwarding to dead-letter topics | Cloud Pub/Sub". Google Cloud. Retrieved 2020-12-26.
- ^ spelluru. "Compare Azure messaging services". docs.microsoft.com. Retrieved 2020-01-17.
- ^ Böhm-Mäder, Johannes. WebSphere MQ Security: Tales of Scowling Wolves Among Unglamorous Sheep. BoD. p. 68. ISBN 3842381506.
- ^ "Solace Dead Message Queues".
- ^ "Apache Kafka documentation".
- ^ "Apache Pulsar documentation".
- ^ "Apache Pulsar PIP-22:Dead Letter Topic".
Categories:
- Inter-process communication
- Events (computing)