1
00:00:00,540 --> 00:00:05,580
In this video, we are going to talk about how does a lambda works?

2
00:00:06,060 --> 00:00:11,640
Last video we said that a lambda fits into event driven architectures.

3
00:00:11,820 --> 00:00:18,810
So as you can see the image, a lambda triggers by event and executes the function code.

4
00:00:19,290 --> 00:00:21,810
But how does a lambda works?

5
00:00:21,840 --> 00:00:25,510
Each lambda function run in its own container.

6
00:00:25,530 --> 00:00:30,570
So you can think every lambda function is a standalone docker containers.

7
00:00:30,990 --> 00:00:37,560
When a function is created, lambda packages it into a new container and then executes that container

8
00:00:37,560 --> 00:00:44,220
on a multi region cloud cluster of servers managed by a year before the functions start running.

9
00:00:44,250 --> 00:00:48,960
Each functions container is allocated its necessary RAM and CPU capacity.

10
00:00:48,990 --> 00:00:52,680
That parameter is also configurable in a lambda.

11
00:00:53,310 --> 00:01:00,720
So when the function finished to running there is a calculation the allocated ram and the function execution

12
00:01:00,720 --> 00:01:05,370
time is multiplied and calculated charge cost for the customer.

13
00:01:05,670 --> 00:01:12,000
So that means customer charge based on the allocated memory and the amount of the execution time the

14
00:01:12,000 --> 00:01:13,110
function finished.

15
00:01:13,680 --> 00:01:18,250
Ada place lambdas entire infrastructure layer is managed by a place.

16
00:01:18,360 --> 00:01:24,510
Clients don't get a lot of visibility into how the system is running, but they are also don't need

17
00:01:24,510 --> 00:01:30,510
to know about underlying machine network contention and so on, so they don't have to worry about things

18
00:01:30,510 --> 00:01:33,240
like Ada handle this itself.

19
00:01:33,750 --> 00:01:41,070
So using a lambda can save your time on operational task because the service is fully managed.

20
00:01:41,430 --> 00:01:47,160
So when there is no infrastructure to maintain, you can spend more time on application code and your

21
00:01:47,160 --> 00:01:48,630
actual business logics.

22
00:01:48,630 --> 00:01:49,620
That means it.

23
00:01:49,620 --> 00:01:52,860
Giving up the flexibility about your infrastructure.

24
00:01:52,890 --> 00:01:58,800
You only think about uploading your code which is encoding to your business logic and you don't worry

25
00:01:58,800 --> 00:02:03,000
about the underlying infrastructure network and communication.

26
00:02:03,000 --> 00:02:06,000
All things handled by the ADA Willis Cloud.