In this video, we are going to talk about how does a lambda works?
Last video we said that a lambda fits into event driven architectures.
So as you can see the image, a lambda triggers by event and executes the function code.
But how does a lambda works?
Each lambda function run in its own container.
So you can think every lambda function is a standalone docker containers.
When a function is created, lambda packages it into a new container and then executes that container
on a multi region cloud cluster of servers managed by a year before the functions start running.
Each functions container is allocated its necessary RAM and CPU capacity.
That parameter is also configurable in a lambda.
So when the function finished to running there is a calculation the allocated ram and the function execution
time is multiplied and calculated charge cost for the customer.
So that means customer charge based on the allocated memory and the amount of the execution time the
function finished.
Ada place lambdas entire infrastructure layer is managed by a place.
Clients don't get a lot of visibility into how the system is running, but they are also don't need
to know about underlying machine network contention and so on, so they don't have to worry about things
like Ada handle this itself.
So using a lambda can save your time on operational task because the service is fully managed.
So when there is no infrastructure to maintain, you can spend more time on application code and your
actual business logics.
That means it.
Giving up the flexibility about your infrastructure.
You only think about uploading your code which is encoding to your business logic and you don't worry
about the underlying infrastructure network and communication.
All things handled by the ADA Willis Cloud.