1
00:00:00,330 --> 00:00:07,530
In this video, we are going to talk about API Gateway as a Lambda Synchronous Event sources.

2
00:00:08,430 --> 00:00:11,820
So synchronous commands are request and response.

3
00:00:11,850 --> 00:00:16,830
In a synchronous model, the client makes a request and waits for a response.

4
00:00:16,860 --> 00:00:22,830
API Gateway is a synchronous event source and provides a Solus API proxy to ADA Lambda.

5
00:00:23,010 --> 00:00:29,340
Synchronous commands are a relatively simple interaction to common create, read, update and delete.

6
00:00:29,340 --> 00:00:31,260
That means crud API actions.

7
00:00:31,590 --> 00:00:38,010
The advantage of this approach is the immediate response to our API calls, so we can also use the API

8
00:00:38,010 --> 00:00:41,610
in order to control aspects of the request and the response.

9
00:00:41,670 --> 00:00:47,940
Examples are validating the characteristic of the request before the consumer process it or reformatting

10
00:00:47,940 --> 00:00:49,980
the response before passing to the client.

11
00:00:49,980 --> 00:00:52,650
We can use API gateway in these scenarios.

12
00:00:53,340 --> 00:00:59,400
The disadvantage is that if something goes wrong or takes a long time to the downstream services, the

13
00:00:59,400 --> 00:01:01,290
whole process will be blocked.

14
00:01:01,620 --> 00:01:08,850
So as you can see, that API gateway is a synchronous trigger to a lambda that we will also follow the

15
00:01:08,910 --> 00:01:13,320
use case when developing our serverless microservices CRUD operations.