1
00:00:00,360 --> 00:00:06,090
In this video we are going to learn API, gateway web socket, API, core concepts.

2
00:00:06,750 --> 00:00:12,450
We can say that the main core concepts of web socket API are roots, integration and states.

3
00:00:12,960 --> 00:00:19,120
So in a website API, the client and server can both send message to each other at any time and they

4
00:00:19,140 --> 00:00:19,320
can.

5
00:00:19,320 --> 00:00:25,230
Service can easily push data to connected user and devices, avoiding need to implement complex polling

6
00:00:25,230 --> 00:00:25,970
mechanism.

7
00:00:25,980 --> 00:00:31,740
So it is a collection of web socket roots and the root case that are integrated with the backend HTTP

8
00:00:31,740 --> 00:00:35,100
and lambda functions or other services.

9
00:00:35,640 --> 00:00:42,000
So if you look at the core concepts of web socket API, we can start with the root selection expression

10
00:00:42,150 --> 00:00:47,850
around selection expression tiles API gateway which draw to call when a client send a message.

11
00:00:47,880 --> 00:00:53,580
So API Gateway use the raw selection expression to determine which role to invoke when a client sends

12
00:00:53,580 --> 00:00:54,240
a message.

13
00:00:54,390 --> 00:01:00,270
When your API receives a adjacent message from a client, API, gateway evaluates the root selection

14
00:01:00,270 --> 00:01:03,480
expression and select the row that match the result.

15
00:01:03,750 --> 00:01:11,160
So another important core concept is roads API gateway use rods to expose integrations to the client

16
00:01:11,160 --> 00:01:12,030
applications.

17
00:01:12,240 --> 00:01:18,630
API Gateway evaluates the raw selection expression of our API at runtime to determine which raw to invoke

18
00:01:18,630 --> 00:01:20,400
this incoming event.

19
00:01:20,520 --> 00:01:22,620
So we have two types.

20
00:01:22,980 --> 00:01:25,060
The first one is predefined route.

21
00:01:25,080 --> 00:01:27,120
The second one is custom lots.

22
00:01:28,130 --> 00:01:33,050
So in predefined roles we have connect, disconnect and default routes.

23
00:01:33,320 --> 00:01:37,310
So the connect rod is triggered when a client connects our API.

24
00:01:37,340 --> 00:01:43,850
The disconnect is triggered when either the server or the client close the connections so the default

25
00:01:43,850 --> 00:01:44,840
rod is triggered.

26
00:01:44,840 --> 00:01:50,030
If the rod selection expression can't be evaluated against the message, or if there is no matching

27
00:01:50,030 --> 00:01:51,050
rod is found.

28
00:01:51,930 --> 00:01:57,960
So for customers, in order to invoke a specific integration based on message content, we should create

29
00:01:57,960 --> 00:01:58,950
a customer load.

30
00:01:59,160 --> 00:02:06,690
When an incoming message contains a JSON property API gateway, use our API selection expression to

31
00:02:06,690 --> 00:02:08,570
determine which route to invoke.

32
00:02:08,580 --> 00:02:14,970
So when they evaluate route selection expression match a custom route API gateway invokes the integration

33
00:02:14,970 --> 00:02:17,250
that we attach to the custom route.

34
00:02:18,530 --> 00:02:21,560
So another core concept is attaching integrations.

35
00:02:21,560 --> 00:02:26,840
In order to deploy an API, we must set up at least one route.

36
00:02:27,050 --> 00:02:31,030
All the routes that we set up must have an integration attached.

37
00:02:31,040 --> 00:02:36,490
So in order to set up the integrations, we should, we can select the mode as the integration type

38
00:02:36,500 --> 00:02:37,970
for our routes.

39
00:02:38,120 --> 00:02:41,870
So another important core concept is states.

40
00:02:41,990 --> 00:02:47,320
States are independently configurable environment that are API can be deployed.

41
00:02:47,330 --> 00:02:52,700
So we must deploy to a state for API configuration change to take effect.

42
00:02:52,730 --> 00:02:57,470
We can edit stage the result environment such as development or production.

43
00:02:57,800 --> 00:03:01,780
So now let's create a web socket API with using a measurement console.