1 00:00:00,670 --> 00:00:05,110 In this video, we are going to talk about how Amazon event works. 2 00:00:06,430 --> 00:00:11,470 So basically almost an event which connects applications using the events. 3 00:00:12,280 --> 00:00:18,100 An event is a signal that a system's state has changed, such as the change in the status of the customer 4 00:00:18,100 --> 00:00:25,900 support ticket so customers can integrate their own applications with microservices, sales applications 5 00:00:25,900 --> 00:00:30,790 and customer application as an event source which publish events to the event pass. 6 00:00:31,540 --> 00:00:33,130 You can see the image on the slide. 7 00:00:33,130 --> 00:00:39,430 I'm going to explain this event page architecture from receiving event to the targets to a services 8 00:00:39,430 --> 00:00:45,400 we can see here, receiving event in the source systems and targets to the target systems. 9 00:00:45,880 --> 00:00:47,380 Please follow me on the slide. 10 00:00:47,530 --> 00:00:48,790 So basically. 11 00:00:49,550 --> 00:00:55,970 Almost everyone receives an event, an indicator of the change in environment and applies to rule to 12 00:00:56,150 --> 00:00:58,130 out the event to the target system. 13 00:00:58,790 --> 00:01:05,260 Rules match the events to targets based on either the structure of the event or called an event pattern. 14 00:01:05,270 --> 00:01:10,100 Or we can schedule an event or trigger the downstream target systems. 15 00:01:10,430 --> 00:01:16,730 For example, when the Amazon EC2 instance changed from penning to running, you can have a rule that 16 00:01:16,730 --> 00:01:18,890 sends the event to a lambda function. 17 00:01:20,230 --> 00:01:26,680 All events that come to event which are associated with an event plus rules are tied to a single event 18 00:01:26,680 --> 00:01:30,340 plus, so they can only be applied to events to that event. 19 00:01:30,370 --> 00:01:37,060 Plus, your account has a default event bus which receives events from a services, and you can also 20 00:01:37,060 --> 00:01:42,160 create custom event buses to send or receive events from a different account or region. 21 00:01:43,090 --> 00:01:50,530 You can define a filtering rule to filter events and what events to add service targets and API destinations. 22 00:01:51,470 --> 00:01:58,070 L.A.P.D. Secure Registry Stores schema generated by your organization's applications, edible sources 23 00:01:58,070 --> 00:01:59,810 or any source applications? 24 00:02:01,130 --> 00:02:06,680 A schema includes information such as the title format and validation rules for event data. 25 00:02:06,830 --> 00:02:13,700 You can download code bindings for any schema in the registry in your ID and directly use the type object. 26 00:02:13,700 --> 00:02:15,770 Representation the event in your code. 27 00:02:16,690 --> 00:02:25,030 So which API destinations are HTTP end points that you can set as target as a rule in the same way that 28 00:02:25,030 --> 00:02:32,260 you would like to send data event data to a services or resources by using the API destinations you 29 00:02:32,260 --> 00:02:40,750 can use rest API calls to root events between services, integrated source applications and your applications 30 00:02:40,750 --> 00:02:42,430 outside of the place. 31 00:02:42,970 --> 00:02:48,280 So when you create an API destination, you should specify a connection to use for it. 32 00:02:48,430 --> 00:02:54,190 Each connection includes the details about the authorization type and parameter to use to authorize 33 00:02:54,190 --> 00:02:56,350 with the API destination endpoint. 34 00:02:57,400 --> 00:03:04,270 So you can see in this picture on the slide is you can see that almost an event which has four core 35 00:03:04,270 --> 00:03:10,060 concepts which are the event sources, event bosses rules and the targets. 36 00:03:10,870 --> 00:03:13,330 So these are the four main core concepts. 37 00:03:13,360 --> 00:03:15,460 The first one is the event sources. 38 00:03:15,490 --> 00:03:18,640 Event sources publish events to the event buses. 39 00:03:18,670 --> 00:03:21,040 And the second one is the event buses. 40 00:03:21,070 --> 00:03:25,970 All events that come to event which are associated with the an event bus. 41 00:03:26,200 --> 00:03:27,910 So the third one is the rules. 42 00:03:27,910 --> 00:03:34,300 Rules basically match events to targets based on either the structure of the event or called any event 43 00:03:34,300 --> 00:03:39,340 pattern or using the scheduled patterns that trigger the targets. 44 00:03:39,370 --> 00:03:41,320 And the last one is the target. 45 00:03:41,590 --> 00:03:47,710 Filtering the rule to filter events and route events to the target services and AP destinations. 46 00:03:48,970 --> 00:03:55,840 So when you build serverless applications with using event, which it can be helpful to know the event 47 00:03:55,840 --> 00:03:59,350 pattern of typical events without having to generate the event. 48 00:03:59,680 --> 00:04:05,860 The event patterns are described in schemas which are available for all events generated by the ADA 49 00:04:05,860 --> 00:04:07,600 Relay Services on Event Bridge. 50 00:04:08,230 --> 00:04:14,970 So you can also create or upload custom schemas for events that don't come from the ADA services. 51 00:04:15,010 --> 00:04:21,010 Once you have a schema for an event, you can download code bindings for popular programming languages. 52 00:04:21,800 --> 00:04:28,550 We will also use Amazon event for decoupling or basket and or microservices and routing events between 53 00:04:28,550 --> 00:04:32,780 these microservices when developing our serverless ecommerce application. 54 00:04:33,080 --> 00:04:37,310 In the next video we are going to talk about Amazon event core concepts.