In this video we are going to learn Ada Lovelace Lambda Use cases for invocation types.
So Lambda Functions articles are the core components of building applications on a lambda.
A lambda function is the code and the runtime that process the events.
While a trigger is the service that invokes the function, you can see the image on the slide.
Let me say one by one the example use cases.
The first use case is file processing.
Suppose that you have a photo sharing application.
People use application to upload photos and the application application stores these user photos in
the Amazon S3 bucket.
Then our application creates a thumbnail version of each user photos and display them on the user's
profile page.
For that purpose, we will use the Amazon S3 event, which is the uploaded object into bucket event
and triggered the lambda function.
And another use case is data and analytics.
So you can think that we are building an analytic application and storing raw data in dynamic DB table.
So when you write update or delete items in a table dynamo DB C teams can publish item and update event
to stream and invoke the lambda function.
And another use case is the web application.
And suppose that you are creating a website and you want to host the back end logic on lambda so we
can invoke our lambda function over the HTTP using the Amazon API gateway with the HTTP endpoint.
And another use case could be the mobile application.
And think about that.
We have a custom mobile application that produced the events and we can create a lambda function to
process these events published by our mobile applications.
So it is Lambda supports main services as an event sources.
When you configure these event sources to trigger a lambda function, the lambda function is invoked
automatically when events occur.
So we can also define event source mapping, which is how you identify what events to take and which
lambda function is to invoke.
So far we only see the lambda invocations with synchronous way.
From now on we will develop lambda functions be triggered asynchronously and even source mapping invocations.
So according to different invocation types, we will implement two hands on labs.
The first one is the Amazon.
S3 pushes the events and invokes a Lambda function.
Amazon S3 can publish event of different types of actions like put post copy and delete object events
on a bucket.
Using the bucket notification feature, we can configure an event source mapping that directs to Amazon
S3 to invoke a lambda function when a specific type of the event occurs.
So this is the first hansen-love and the second time zone loop is the address.
Lambda pulls the event from a kinesis or Dynamo DB streams and invokes a lambda function for pol based
event sources.
Edible Islam, the pulse, the source and then invokes the lambda function when records are detected
on that source.
So you can see the image on the slide.
The first hands on lab is the Amazon S3 asynchronous.
The trigger is lambda when uploading an image, and the second handle is the event source mapping.
Pulling in location, we add item into Q, which will be the Amazon case Q and this will be a pull from
the Lambda and invoke a function.
And also there will be a dynamic DB.
Dynamic DB streams happened and after that this stream will be pulled from the database lambda and invoke
the function.