[英]What is the difference between Azure Dead Letter Queues and Poison Queues when using Storage Queue and Service Bus?
What is the difference between Azure Dead letter queue and Poison queue with respect to Storage Queue and Service Bus? Azure 死信队列和毒药队列在存储队列和服务总线方面有什么区别?
How do I read the messages from those queues?如何从这些队列中读取消息?
A poison message is a message that is sent to the queue or topic that the consuming application cannot process correctly.有害消息是发送到消费应用程序无法正确处理的队列或主题的消息。
Once the DeliveryCount
of these messages reaches the MaxDeliveryCount
of the queue/topic, they will then be classed as poison messages .一旦这些消息的
DeliveryCount
达到队列/主题的MaxDeliveryCount
,它们就会被归类为有害消息。
These messages will be sent to a queue called <originalqueuename>-poison
.这些消息将被发送到一个名为
<originalqueuename>-poison
的队列。
Both Azure Queue Storage & Azure Service Bus support poison messages but Azure Queue Storage does not support automatic dead-lettering. Azure 队列存储和 Azure 服务总线都支持有害消息,但 Azure 队列存储不支持自动死信。
This means that while in Azure Service Bus you can set expired messages to be moved into a DLQ for later processing, messages with a TTL value that expire in Azure Queue Storage will be deleted permanently.这意味着,虽然在 Azure 服务总线中,您可以将过期的消息设置为移动到 DLQ 以供以后处理,但在 Azure 队列存储中具有过期的 TTL 值的消息将被永久删除。
Otherwise, handling of messages that will "poison" the system & can never be consumed, is pretty much the same in both offerings.否则,处理会“毒害”系统并且永远不会被消耗的消息在两种产品中几乎相同。
One offers a poison queue and one offers a DLQ.一种提供毒药队列,另一种提供 DLQ。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.