In this video, we are going to learn a lot of the event sources and the destination critical sources.
With a w slumdog, we can run the code for virtually any type of applications or services, all with
zero administration, upload our code and run our code and scale our code automatically with high availability.
So we can also set up our Lambda Code to automatically trigger from other sources or call it directly
from any web or mobile application.
The typical lambda function.
There is an event, source or trigger and the actual function code and then there is a destination.
You can see the image on the slide here.
Main three three parts of the ID will Islam the invocation that should be an event source or trigger.
And here you can see the actual function code.
And then after that there is a destination that is direct from the lambda function.
So you can see the image on the slide.
We have even sought source, function and destination.
So a lot of the integrates with other sources to invoke functions or take other actions.
So the event source has a number of services that can directly interact with slums, and these events
can be almost anything.
They can be an HTTP call or cron job, they can be uploading an object into S3 bucket, they can be
changed in a resource state, or they can be a third party call like payment down through Stripe.
So the event is something that happens that triggered to a lambda function to execute.
After triggering event to the lambda function, Lambda launched the execution environment with different
language and runtimes.
We can basically develop any language and runtime into lambda function code after execution.
Lambda has destinations that can be interaction with our function code.
It depends on our function, business logic and business requirements.
So if you look at the use case of the integrations, we can say that Adobe Islam integrates with other
services in order to invoke functions or take other actions.
There are some common use cases and we can say that invoke a function in response to the source lifecycle
event like with Amazon S3.
This is using a base lambda with Amazon S3 for example, one and one an object upload to S3 bucket.
This event can be triggered a lambda function.
We will do this example in a hands on loop in the upcoming videos and the second use case could be responding
to incoming HTTP request.
This is using lambda with API gateway.
Typical rest API use cases can be triggered API gateway and response back to client.
And another use case could be the consume event from a.
This is using lambda with Amazon squiz lambda pulls to queue records from the Amazon SGS and another
use case is run a function on a schedule.
This is using a double Islam with Amazon event with cloud watch events.
So depending on which service you are using with later as Lambda, the invocation generally works in
one or two ways and even drives the invocation or lambda posts a queue or data streams and invokes the
function in a response to activity in the queue or data stream.
Here you can see the list of services lambda event sources.
You can find the list of the services that invokes to a lambda as an event source.
And you can see these following table in the slide in order to determine which method of the invocation
we should use.
And you can use these following link from the service name to find information about how to set up the
integration between services and with database lambda.
So these topics also include the example events that we can use the test or function, and we will also
see all these different services and invocation types in the upcoming videos.