1
00:00:00,210 --> 00:00:06,630
In this section, we are going to do hands on up inventory with Microsoft's architecture using Amazon

2
00:00:06,630 --> 00:00:08,820
event, which is aqueous and lambda.

3
00:00:09,300 --> 00:00:14,490
So we will see how to decouple microservices with events using the Amazon event bridge.

4
00:00:15,120 --> 00:00:18,870
Let's directly look at the internal architecture for our Hands-On Update.

5
00:00:18,870 --> 00:00:21,240
We use the publisher Scribe Panel pattern.

6
00:00:21,720 --> 00:00:23,280
You can see the image on the slide.

7
00:00:23,280 --> 00:00:29,790
Basically we are following the ecommerce architecture and use case is basket checkout event one user

8
00:00:29,790 --> 00:00:30,660
checkout to basket.

9
00:00:30,660 --> 00:00:35,100
This will trigger an event to event page and consume from the ordering microservices.

10
00:00:35,100 --> 00:00:40,710
So there is a couple of microservices which implement ecommerce modules over the product basket and

11
00:00:40,710 --> 00:00:42,030
ordering microservices.

12
00:00:42,210 --> 00:00:47,010
We will use a lambda service as a microservice and use power of lambda function.

13
00:00:47,550 --> 00:00:48,390
Let me explain.

14
00:00:48,390 --> 00:00:54,240
Basket Lambda Microservices Basket Microservices triggers to event driven use case which is the checkout

15
00:00:54,240 --> 00:00:56,520
basket one checkout basket.

16
00:00:56,550 --> 00:01:02,070
This will publish and create event to service event bus, which is the Amazon event page.

17
00:01:02,070 --> 00:01:07,170
And this is the asynchronous communication we'll have by the basket Lambda Microservices and Amazon

18
00:01:07,170 --> 00:01:12,540
event page and consumed by the ordering microservices over the A case.

19
00:01:13,050 --> 00:01:19,290
So Amazon event pitch asynchronous communication held by the soulless event pass and we will create

20
00:01:19,290 --> 00:01:24,150
the rules and target definitions for Amazon event page from the basket of microservices.

21
00:01:24,150 --> 00:01:29,820
That means we will develop basket microservices one publishing checkout message to Amazon event page

22
00:01:29,820 --> 00:01:33,600
with using the SDK libraries for development purpose.

23
00:01:34,170 --> 00:01:39,540
So if we look at the CSS and ordering Lambda Microservices after publishing checkout event two event

24
00:01:39,540 --> 00:01:48,120
which this event will consume by the ordering path event sent to event to Amazon in order to gain power

25
00:01:48,120 --> 00:01:49,890
of to a queue.

26
00:01:50,070 --> 00:01:55,170
After that ordering Lambda Microservices will consume this event with polling invocations.

27
00:01:55,170 --> 00:02:00,750
That means we will use a one source mapping communication type here when consuming events, ordering

28
00:02:00,750 --> 00:02:07,200
lambda microservices and pulling requests and get event from the queue after consuming the event from

29
00:02:07,200 --> 00:02:13,740
the queue or the Lambda Microservices process, the event with the creating order record into its Dynamo

30
00:02:13,740 --> 00:02:14,610
DB table.

31
00:02:14,730 --> 00:02:19,980
So ordering Lambda Microservice perform all these operations, we developing Lambda functions and using

32
00:02:19,980 --> 00:02:26,130
the SDK libraries so we will develop together and step by step in this video.

33
00:02:26,310 --> 00:02:27,030
Okay.

34
00:02:27,030 --> 00:02:33,060
So if you look at the communication patterns, we have also followed the communication pattern and best

35
00:02:33,060 --> 00:02:39,410
practices when designing soulless microservice communication for synchronous asynchronous and also event

36
00:02:39,450 --> 00:02:40,320
source mapping.

37
00:02:40,320 --> 00:02:47,400
We are using the Amazon API gateway Amazon Event Bridge as an event pass and also Amazon is using as

38
00:02:47,400 --> 00:02:48,600
a queue service.

39
00:02:48,600 --> 00:02:54,210
So we will use API gateway for restful API driven development and synchronous event sources.

40
00:02:54,210 --> 00:02:59,340
We will use event bridge for event driven asynchronous communication between microservices.

41
00:02:59,340 --> 00:03:05,040
We will use case for decoupled microservices and process events asynchronously using to use.

42
00:03:05,910 --> 00:03:11,870
So in this section we will learn how to publish subscribe pattern apply using with Amazon event page

43
00:03:11,870 --> 00:03:15,350
and space that enables asynchronous message communication.

44
00:03:15,350 --> 00:03:21,260
When we link distributed microservice architectures, there is no debt that we implement in architectural

45
00:03:21,260 --> 00:03:21,790
networks.

46
00:03:21,830 --> 00:03:23,180
We have two main steps.

47
00:03:23,300 --> 00:03:29,900
The first step is create infrastructure on the cloud and the second step is the actual lambda function

48
00:03:29,900 --> 00:03:35,360
code and interacting with the squares, event bridge and so on using the SDK libraries.

49
00:03:35,570 --> 00:03:41,570
So we will start with the first step, which is to create this infrastructure on a lot.

50
00:03:41,570 --> 00:03:45,830
But before that let's start to remember event driven microservice architectures.