In this video, we are going to talk about how Amazon event works.
So basically almost an event which connects applications using the events.
An event is a signal that a system's state has changed, such as the change in the status of the customer
support ticket so customers can integrate their own applications with microservices, sales applications
and customer application as an event source which publish events to the event pass.
You can see the image on the slide.
I'm going to explain this event page architecture from receiving event to the targets to a services
we can see here, receiving event in the source systems and targets to the target systems.
Please follow me on the slide.
So basically.
Almost everyone receives an event, an indicator of the change in environment and applies to rule to
out the event to the target system.
Rules match the events to targets based on either the structure of the event or called an event pattern.
Or we can schedule an event or trigger the downstream target systems.
For example, when the Amazon EC2 instance changed from penning to running, you can have a rule that
sends the event to a lambda function.
All events that come to event which are associated with an event plus rules are tied to a single event
plus, so they can only be applied to events to that event.
Plus, your account has a default event bus which receives events from a services, and you can also
create custom event buses to send or receive events from a different account or region.
You can define a filtering rule to filter events and what events to add service targets and API destinations.
L.A.P.D. Secure Registry Stores schema generated by your organization's applications, edible sources
or any source applications?
A schema includes information such as the title format and validation rules for event data.
You can download code bindings for any schema in the registry in your ID and directly use the type object.
Representation the event in your code.
So which API destinations are HTTP end points that you can set as target as a rule in the same way that
you would like to send data event data to a services or resources by using the API destinations you
can use rest API calls to root events between services, integrated source applications and your applications
outside of the place.
So when you create an API destination, you should specify a connection to use for it.
Each connection includes the details about the authorization type and parameter to use to authorize
with the API destination endpoint.
So you can see in this picture on the slide is you can see that almost an event which has four core
concepts which are the event sources, event bosses rules and the targets.
So these are the four main core concepts.
The first one is the event sources.
Event sources publish events to the event buses.
And the second one is the event buses.
All events that come to event which are associated with the an event bus.
So the third one is the rules.
Rules basically match events to targets based on either the structure of the event or called any event
pattern or using the scheduled patterns that trigger the targets.
And the last one is the target.
Filtering the rule to filter events and route events to the target services and AP destinations.
So when you build serverless applications with using event, which it can be helpful to know the event
pattern of typical events without having to generate the event.
The event patterns are described in schemas which are available for all events generated by the ADA
Relay Services on Event Bridge.
So you can also create or upload custom schemas for events that don't come from the ADA services.
Once you have a schema for an event, you can download code bindings for popular programming languages.
We will also use Amazon event for decoupling or basket and or microservices and routing events between
these microservices when developing our serverless ecommerce application.
In the next video we are going to talk about Amazon event core concepts.