In this video.
We are going to talk about amazon six days later cuz.
I was on the case supports the data queues which other queue can target for messages that cannot be
processed or consumed successfully.
They little cues are useful for debugging your application or messaging system because they let you
isolate and consume message to determine why their processing doesn't succeed.
So how do the little cues works?
Sometimes message cannot be processed because of the variety of possible issues.
For example, anonymous conditions within the producer or consumer application or unexpected exceptions
can be caused an issue with your application code.
For example, if a user place, a web order with a particular product ID and if the product ID is delayed,
the web store code fails and display an error.
And the message with the order request is sent to a dead letter queue.
Occasionally producers and consumers might fail to interpret aspects of the protocol that they use to
communicate, causing message, corruptions or loss.
Also, the consumers hardware errors might corrupt message payloads.
So what are the benefits of the cues?
The main task of a data queue is to handle the lifecycle of unconsumed methods.
A digital queue lets you set aside an isolate message that cannot be processed correctly in order to
determine why the processing didn't succeed.
And we can setting up the data queue and it allows you to configure an alarm for any message, move
to the digital queue and it is provided to examine logs for exceptions that might have caused the message
to be moved to the dedicated queue.
And also we can analyse the contents of message, move to the data queue to diagnose software or the
producer or consumer hardware issues.
And of course we can determine whether you have given your consumers sufficient time to process messages.
And then the third queue is a good, good feature we can use.
Amazon is in that data queue for the best practices and the unconsumed message can be followed from
the detector queues.