1
00:00:00,450 --> 00:00:07,080
In this video, we are going to talk about Amazon creates architecture and explains the lifecycle of

2
00:00:07,080 --> 00:00:08,730
the Amazon message.

3
00:00:09,700 --> 00:00:14,020
So in this video, we will see the parts of a distributed messaging system.

4
00:00:15,200 --> 00:00:16,910
You can see the image on the slide.

5
00:00:16,940 --> 00:00:19,760
There are three main parts in Amazon case.

6
00:00:19,940 --> 00:00:22,400
The first part is producers.

7
00:00:22,640 --> 00:00:24,410
Or we can say publishers.

8
00:00:24,440 --> 00:00:27,260
The components that send message to the queue.

9
00:00:27,410 --> 00:00:29,870
And the second part is consumers.

10
00:00:30,260 --> 00:00:33,200
These components that receive message from the queue.

11
00:00:33,380 --> 00:00:37,910
And the third part is actual queue, the queue which holds the message.

12
00:00:38,240 --> 00:00:40,600
So almost in this case, hold the message.

13
00:00:40,610 --> 00:00:45,200
Redundantly stores the message across multiple Amazon servers.

14
00:00:47,530 --> 00:00:54,340
So if you look at the message lifecycle of Amazon message, we can see the image on the slide.

15
00:00:54,370 --> 00:00:57,340
Amazon message from creation to deletion.

16
00:00:57,400 --> 00:01:01,240
This is the lifecycle of an Amazon message in the queue.

17
00:01:01,570 --> 00:01:09,580
So the first part, the first step, a producer that means component one sent message sent message A

18
00:01:09,610 --> 00:01:10,120
to Q.

19
00:01:10,150 --> 00:01:17,050
We can see in here the component one sent a message to the queue and the message is distributed across

20
00:01:17,050 --> 00:01:19,660
the Amazon service redundantly.

21
00:01:20,450 --> 00:01:28,490
And the second step, a consumer in our case, component two is ready to process message, and it basically

22
00:01:28,490 --> 00:01:33,080
consumes message from the Q and message A is returned.

23
00:01:34,370 --> 00:01:41,510
While Message A is being processed, it remains in the queue and isn't returned to subsequent receive

24
00:01:41,510 --> 00:01:44,580
requests for the duration of the visibility timeout.

25
00:01:44,600 --> 00:01:52,280
So that means one component to processing to a no one can receive the a message in the visible to timeout.

26
00:01:53,320 --> 00:01:56,720
The last step is the third step is the consumer.

27
00:01:56,740 --> 00:02:03,490
That means compared to deletes the message a from the queue to prevent the message from being received

28
00:02:03,490 --> 00:02:06,820
and processed again when the visibility timeout expires.