1
00:00:00,490 --> 00:00:01,660
In this video.

2
00:00:01,750 --> 00:00:06,010
We are going to talk about amazon six days later cuz.

3
00:00:07,020 --> 00:00:13,760
I was on the case supports the data queues which other queue can target for messages that cannot be

4
00:00:13,760 --> 00:00:15,980
processed or consumed successfully.

5
00:00:17,490 --> 00:00:23,700
They little cues are useful for debugging your application or messaging system because they let you

6
00:00:23,700 --> 00:00:28,500
isolate and consume message to determine why their processing doesn't succeed.

7
00:00:30,070 --> 00:00:32,350
So how do the little cues works?

8
00:00:32,530 --> 00:00:37,570
Sometimes message cannot be processed because of the variety of possible issues.

9
00:00:37,570 --> 00:00:44,680
For example, anonymous conditions within the producer or consumer application or unexpected exceptions

10
00:00:44,680 --> 00:00:47,530
can be caused an issue with your application code.

11
00:00:49,340 --> 00:00:56,750
For example, if a user place, a web order with a particular product ID and if the product ID is delayed,

12
00:00:56,750 --> 00:00:59,690
the web store code fails and display an error.

13
00:00:59,810 --> 00:01:03,590
And the message with the order request is sent to a dead letter queue.

14
00:01:04,320 --> 00:01:10,560
Occasionally producers and consumers might fail to interpret aspects of the protocol that they use to

15
00:01:10,560 --> 00:01:13,410
communicate, causing message, corruptions or loss.

16
00:01:13,530 --> 00:01:17,400
Also, the consumers hardware errors might corrupt message payloads.

17
00:01:18,600 --> 00:01:21,300
So what are the benefits of the cues?

18
00:01:21,510 --> 00:01:26,610
The main task of a data queue is to handle the lifecycle of unconsumed methods.

19
00:01:28,070 --> 00:01:34,390
A digital queue lets you set aside an isolate message that cannot be processed correctly in order to

20
00:01:34,390 --> 00:01:37,420
determine why the processing didn't succeed.

21
00:01:38,080 --> 00:01:44,320
And we can setting up the data queue and it allows you to configure an alarm for any message, move

22
00:01:44,320 --> 00:01:50,230
to the digital queue and it is provided to examine logs for exceptions that might have caused the message

23
00:01:50,230 --> 00:01:52,060
to be moved to the dedicated queue.

24
00:01:52,240 --> 00:01:58,570
And also we can analyse the contents of message, move to the data queue to diagnose software or the

25
00:01:58,570 --> 00:02:00,970
producer or consumer hardware issues.

26
00:02:00,970 --> 00:02:06,730
And of course we can determine whether you have given your consumers sufficient time to process messages.

27
00:02:07,180 --> 00:02:10,780
And then the third queue is a good, good feature we can use.

28
00:02:10,780 --> 00:02:17,440
Amazon is in that data queue for the best practices and the unconsumed message can be followed from

29
00:02:17,440 --> 00:02:18,490
the detector queues.