In this video, we are going to see how using a double standard with other services Lambda is on demand
compute service that runs custom code in response to the events.
Most services generate events and many can act as an even source for lambda function.
So edibles.
Lambda integrates with other services to invoke functions and take other actions.
As you remember that in the last video we have the Lambda Invocation types, and according to Invocation
types, Lambda can be invoked from the different services.
For that purpose, we can see the list of services that triggered the lambda function from the ADA documentation.
If you open the ADA documentation about using ADA Wilson with other services and if you scroll down,
you can see the services that is basically integrate and trigger the lambda function.
So here you can see the synchronous invocation, asynchronous invocation and lambda pulling for different
invocations from different services can happen for the event source.
Let me start with synchronous invocation.
Synchronous invocation is almost an API gateway that we already see how to trigger Amazon API gateway
to Lambda function and develop our function.
You can see the example.
Imagine if you come to asynchronous invocation, these will be the.
I was on simple search service.
If you open these Amazon S3 and scroll down, you can see the example event.
JSON comes from the Amazon S3 to invoke the Lambda function.
So if you come back to our list, the last invocation type is the Lambda Polling, which is the event
source mapping invocation.
And the example is the asks Amazon Simple Queue Service.
If you open this example, you can also see the example Amazon case message event that triggered the
lambda function.
So basically, as you can see that we have understood how we are using with using some of with other
services.
So during the course so far we have only see the synchronous invocation for lambda functions.
So rest of the course we will focus on asynchronous and even source mapping invocations.