1
00:00:00,660 --> 00:00:05,990
In this video, we are going to talk about benefits of Amazon event page.

2
00:00:06,240 --> 00:00:13,650
The first benefit is we link event driven architectures event, which basically simplifies the process

3
00:00:13,650 --> 00:00:17,380
of building event driven architectures with the event bridge.

4
00:00:17,400 --> 00:00:24,030
Your event targets don't need to be aware of the event sources because you can filter and publish directly

5
00:00:24,030 --> 00:00:25,020
to the event bridge.

6
00:00:26,200 --> 00:00:27,820
There is no setup required.

7
00:00:27,910 --> 00:00:33,970
It improves developer agility as well as the application resiliency with following to lose decoupled

8
00:00:33,970 --> 00:00:35,500
event driven architectures.

9
00:00:36,280 --> 00:00:43,900
The second benefit is connect source applications, which ingest data from the supported source applications

10
00:00:43,900 --> 00:00:47,290
and routes it to the sources and the source targets.

11
00:00:48,160 --> 00:00:54,690
Of course it is using through the API destinations and HTTP in location endpoint targets for events

12
00:00:54,700 --> 00:00:57,190
without writing any custom integration code.

13
00:00:57,760 --> 00:01:04,240
So you can use event bridge to connect your source applications or use events from your source applications

14
00:01:04,240 --> 00:01:08,500
to trigger workflows for customer supports, business operations and so on.

15
00:01:10,220 --> 00:01:16,860
And another benefit is write less custom code, which makes it easier to connect applications.

16
00:01:16,880 --> 00:01:21,680
You can ingest, filter, transform and deliver events without writing custom code.

17
00:01:22,130 --> 00:01:28,580
The Language Schema Registry supports a collection of easy to find event schemas and enables you to

18
00:01:28,580 --> 00:01:35,720
download code bindings for those schemas in your ID so you can basically represent events as a strong

19
00:01:35,720 --> 00:01:37,370
type object in your code.

20
00:01:37,850 --> 00:01:43,370
It is automatically added schemas discovered from your event bus to the registry through the schema

21
00:01:43,370 --> 00:01:44,570
discovery feature.

22
00:01:46,240 --> 00:01:50,050
Another benefit is reduce operational overhead with the event.

23
00:01:50,510 --> 00:01:53,570
There are no servers to provision, patch and manage.

24
00:01:53,600 --> 00:01:59,870
There is no additional software to install, maintain or operate event which automatically scales based

25
00:01:59,870 --> 00:02:02,060
on the number of the event ingested.

26
00:02:02,150 --> 00:02:09,530
And you pay only for events published by your ADA or SaaS applications event which has built in distribute

27
00:02:09,530 --> 00:02:11,540
availability and tolerance.

28
00:02:11,690 --> 00:02:17,960
Event Village also has a native event archive and replay capability that makes it easy to recover from

29
00:02:17,960 --> 00:02:21,860
the failures or build any application state from all events.

30
00:02:22,010 --> 00:02:26,600
So in the next video, we are going to talk about how Amazon event pages works.