Английская Википедия:Dead letter queue
Шаблон:Short description In message queueing a dead letter queue (DLQ) is a service implementation to store messages that the messaging system cannot or should not deliver.[1] Although implementation-specific, messages can be routed to the DLQ for the following reasons:
- The message is sent to a queue that does not exist.[2][3]
- The maximum queue length is exceeded.
- The message exceeds the size limit.
- The message expires because it reached the TTL (time to live)[4]
- The message is rejected by another queue exchange.[5]
- The message has been read and rejected too many times.[6]
Routing these messages to a dead letter queue enables analysis of common fault patterns and potential software problems.[7] If a message consumer receives a message that it considers invalid, it can instead forward it an Invalid Message Channel,[8] allowing a separation between application-level faults and delivery failures.
Queueing systems that incorporate dead letter queues include Amazon EventBridge,[9] Amazon Simple Queue Service,[7] Apache ActiveMQ, Google Cloud Pub/Sub,[10] HornetQ, Microsoft Message Queuing,[2] Microsoft Azure Event Grid and Azure Service Bus,[11] WebSphere MQ,[12] Solace PubSub+,[13] Rabbit MQ,[5] Apache Kafka[14] and Apache Pulsar.[15][16]
See also
References
- ↑ Шаблон:Cite web
- ↑ 2,0 2,1 Шаблон:Cite book
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ 5,0 5,1 RabbitMQ dead letter queue Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ 7,0 7,1 Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite book
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web
- ↑ Шаблон:Cite web