1
00:00:00,240 --> 00:00:07,080
In this video, we are going to see how using a double standard with other services Lambda is on demand

2
00:00:07,080 --> 00:00:10,860
compute service that runs custom code in response to the events.

3
00:00:11,010 --> 00:00:16,620
Most services generate events and many can act as an even source for lambda function.

4
00:00:17,070 --> 00:00:17,910
So edibles.

5
00:00:17,910 --> 00:00:23,460
Lambda integrates with other services to invoke functions and take other actions.

6
00:00:23,760 --> 00:00:28,980
As you remember that in the last video we have the Lambda Invocation types, and according to Invocation

7
00:00:28,980 --> 00:00:32,850
types, Lambda can be invoked from the different services.

8
00:00:33,060 --> 00:00:39,320
For that purpose, we can see the list of services that triggered the lambda function from the ADA documentation.

9
00:00:39,330 --> 00:00:45,750
If you open the ADA documentation about using ADA Wilson with other services and if you scroll down,

10
00:00:45,750 --> 00:00:51,030
you can see the services that is basically integrate and trigger the lambda function.

11
00:00:51,120 --> 00:00:56,790
So here you can see the synchronous invocation, asynchronous invocation and lambda pulling for different

12
00:00:56,790 --> 00:01:01,470
invocations from different services can happen for the event source.

13
00:01:01,470 --> 00:01:03,270
Let me start with synchronous invocation.

14
00:01:03,270 --> 00:01:09,060
Synchronous invocation is almost an API gateway that we already see how to trigger Amazon API gateway

15
00:01:09,090 --> 00:01:11,490
to Lambda function and develop our function.

16
00:01:11,490 --> 00:01:12,420
You can see the example.

17
00:01:12,420 --> 00:01:16,350
Imagine if you come to asynchronous invocation, these will be the.

18
00:01:17,470 --> 00:01:18,990
I was on simple search service.

19
00:01:19,000 --> 00:01:24,820
If you open these Amazon S3 and scroll down, you can see the example event.

20
00:01:24,820 --> 00:01:28,660
JSON comes from the Amazon S3 to invoke the Lambda function.

21
00:01:28,750 --> 00:01:34,090
So if you come back to our list, the last invocation type is the Lambda Polling, which is the event

22
00:01:34,090 --> 00:01:35,620
source mapping invocation.

23
00:01:35,620 --> 00:01:39,720
And the example is the asks Amazon Simple Queue Service.

24
00:01:39,730 --> 00:01:46,030
If you open this example, you can also see the example Amazon case message event that triggered the

25
00:01:46,220 --> 00:01:47,140
lambda function.

26
00:01:47,440 --> 00:01:54,940
So basically, as you can see that we have understood how we are using with using some of with other

27
00:01:54,940 --> 00:01:55,750
services.

28
00:01:55,750 --> 00:02:02,880
So during the course so far we have only see the synchronous invocation for lambda functions.

29
00:02:02,890 --> 00:02:08,350
So rest of the course we will focus on asynchronous and even source mapping invocations.