1
00:00:00,330 --> 00:00:06,840
In this video, we are going to learn a lot of the event sources and the destination critical sources.

2
00:00:07,710 --> 00:00:13,890
With a w slumdog, we can run the code for virtually any type of applications or services, all with

3
00:00:13,890 --> 00:00:22,230
zero administration, upload our code and run our code and scale our code automatically with high availability.

4
00:00:22,260 --> 00:00:29,370
So we can also set up our Lambda Code to automatically trigger from other sources or call it directly

5
00:00:29,370 --> 00:00:31,770
from any web or mobile application.

6
00:00:33,210 --> 00:00:34,800
The typical lambda function.

7
00:00:34,800 --> 00:00:41,220
There is an event, source or trigger and the actual function code and then there is a destination.

8
00:00:41,430 --> 00:00:44,040
You can see the image on the slide here.

9
00:00:44,040 --> 00:00:50,820
Main three three parts of the ID will Islam the invocation that should be an event source or trigger.

10
00:00:50,910 --> 00:00:54,330
And here you can see the actual function code.

11
00:00:54,330 --> 00:00:59,130
And then after that there is a destination that is direct from the lambda function.

12
00:00:59,870 --> 00:01:01,680
So you can see the image on the slide.

13
00:01:01,700 --> 00:01:05,090
We have even sought source, function and destination.

14
00:01:05,860 --> 00:01:12,280
So a lot of the integrates with other sources to invoke functions or take other actions.

15
00:01:12,430 --> 00:01:18,400
So the event source has a number of services that can directly interact with slums, and these events

16
00:01:18,400 --> 00:01:19,990
can be almost anything.

17
00:01:20,020 --> 00:01:27,310
They can be an HTTP call or cron job, they can be uploading an object into S3 bucket, they can be

18
00:01:27,310 --> 00:01:33,040
changed in a resource state, or they can be a third party call like payment down through Stripe.

19
00:01:33,040 --> 00:01:38,740
So the event is something that happens that triggered to a lambda function to execute.

20
00:01:39,370 --> 00:01:45,220
After triggering event to the lambda function, Lambda launched the execution environment with different

21
00:01:45,220 --> 00:01:46,630
language and runtimes.

22
00:01:46,630 --> 00:01:52,360
We can basically develop any language and runtime into lambda function code after execution.

23
00:01:52,360 --> 00:01:56,560
Lambda has destinations that can be interaction with our function code.

24
00:01:56,560 --> 00:02:01,300
It depends on our function, business logic and business requirements.

25
00:02:02,860 --> 00:02:09,400
So if you look at the use case of the integrations, we can say that Adobe Islam integrates with other

26
00:02:09,760 --> 00:02:13,040
services in order to invoke functions or take other actions.

27
00:02:13,060 --> 00:02:19,540
There are some common use cases and we can say that invoke a function in response to the source lifecycle

28
00:02:19,540 --> 00:02:22,660
event like with Amazon S3.

29
00:02:22,720 --> 00:02:29,710
This is using a base lambda with Amazon S3 for example, one and one an object upload to S3 bucket.

30
00:02:29,740 --> 00:02:32,040
This event can be triggered a lambda function.

31
00:02:32,050 --> 00:02:39,790
We will do this example in a hands on loop in the upcoming videos and the second use case could be responding

32
00:02:39,790 --> 00:02:42,160
to incoming HTTP request.

33
00:02:42,190 --> 00:02:44,440
This is using lambda with API gateway.

34
00:02:44,470 --> 00:02:49,150
Typical rest API use cases can be triggered API gateway and response back to client.

35
00:02:49,660 --> 00:02:52,420
And another use case could be the consume event from a.

36
00:02:52,900 --> 00:03:00,490
This is using lambda with Amazon squiz lambda pulls to queue records from the Amazon SGS and another

37
00:03:00,490 --> 00:03:03,160
use case is run a function on a schedule.

38
00:03:03,190 --> 00:03:07,330
This is using a double Islam with Amazon event with cloud watch events.

39
00:03:07,570 --> 00:03:12,850
So depending on which service you are using with later as Lambda, the invocation generally works in

40
00:03:12,850 --> 00:03:20,560
one or two ways and even drives the invocation or lambda posts a queue or data streams and invokes the

41
00:03:20,560 --> 00:03:23,890
function in a response to activity in the queue or data stream.

42
00:03:25,150 --> 00:03:28,710
Here you can see the list of services lambda event sources.

43
00:03:28,720 --> 00:03:33,640
You can find the list of the services that invokes to a lambda as an event source.

44
00:03:33,640 --> 00:03:39,820
And you can see these following table in the slide in order to determine which method of the invocation

45
00:03:39,820 --> 00:03:40,810
we should use.

46
00:03:41,080 --> 00:03:47,350
And you can use these following link from the service name to find information about how to set up the

47
00:03:47,350 --> 00:03:50,950
integration between services and with database lambda.

48
00:03:50,980 --> 00:03:57,640
So these topics also include the example events that we can use the test or function, and we will also

49
00:03:57,640 --> 00:04:01,420
see all these different services and invocation types in the upcoming videos.