1
00:00:00,530 --> 00:00:07,940
In this video, we are going to explain what is serverless with the operational responsibility model.

2
00:00:08,780 --> 00:00:15,830
When we talk about the service, the best way to explain what service is looking to add is operational

3
00:00:15,830 --> 00:00:17,150
responsibility models.

4
00:00:17,810 --> 00:00:23,210
You can think this is a spectrum about responsible to level of aid services.

5
00:00:23,780 --> 00:00:30,560
If you look at the image and if you look at the horizontal way, we can see the traditional on premises

6
00:00:30,560 --> 00:00:35,090
machines, virtual machines, bare metals, hardware devices.

7
00:00:35,090 --> 00:00:41,690
At the beginning of the image you can see in here here the on premises and these are the on premise

8
00:00:41,690 --> 00:00:45,410
machines, virtual machines, base metals, hardware device and so on.

9
00:00:45,800 --> 00:00:52,190
And if you go to the right hand side, you can see the cloud infrastructure, which includes many services

10
00:00:52,190 --> 00:00:54,860
that manage application services on the cloud.

11
00:00:55,660 --> 00:01:02,800
And if you go to last of the right hand side, you can reach the fully serverless services that we don't

12
00:01:02,800 --> 00:01:10,480
any responsible about servers, pages, updates, and also not consider about scaling, reliability

13
00:01:10,480 --> 00:01:12,070
and availability and so on.

14
00:01:12,610 --> 00:01:18,760
And if you look at the vertical way, you can see the separation of the services, compute database

15
00:01:18,760 --> 00:01:23,050
storage message and application integrations, analytics.

16
00:01:23,050 --> 00:01:27,340
And we can also put here API management for Amazon API Gateway.

17
00:01:27,550 --> 00:01:33,980
So these are the services by grouping for a place that we mostly use when developing enterprise level

18
00:01:34,030 --> 00:01:40,090
applications, we can also see this kind of grouping at a the Willis website.

19
00:01:40,090 --> 00:01:45,550
If you open the list at Amazon.com, you can see the product section.

20
00:01:45,550 --> 00:01:51,310
If you see the products, we can see the grouping, the services in here, for example, application

21
00:01:51,310 --> 00:01:56,530
integration including SAP functions, event page, SAS and case.

22
00:01:56,620 --> 00:02:02,980
And also we have complete services which is the Amazon easy to Lambda functions and so on.

23
00:02:02,980 --> 00:02:11,710
So you can see containers, databases, these are the grouping of the services by that Amazon.com.

24
00:02:11,710 --> 00:02:15,790
So according to this grouping, ADA will service evolve by time.

25
00:02:15,790 --> 00:02:22,300
And now in the service part, they have very great services which you don't consider any server management

26
00:02:22,300 --> 00:02:29,290
and scalability issue you can see in here under the service group we have lots of server services that

27
00:02:29,290 --> 00:02:34,660
we don't consider any server management and any scalability availability issues.

28
00:02:34,780 --> 00:02:41,200
So if you look at the services in the service part, you can see in this line.

29
00:02:41,470 --> 00:02:50,110
So basically in the compute part, we will use a Lambda database, we have a standard DB for NoSQL and

30
00:02:50,110 --> 00:02:59,650
also we have our serverless DB for the ERTMS database and we have Amazon S3 for cloud storage and we

31
00:02:59,650 --> 00:03:06,210
have messaging services for application integration, part SAS excuse and event bridge.

32
00:03:06,220 --> 00:03:09,220
And all analytics we have is on alternate.

33
00:03:09,250 --> 00:03:13,030
And also we have API management for Amazon API Gateway.

34
00:03:13,570 --> 00:03:16,840
So we will use lots of these services during the course.

35
00:03:16,840 --> 00:03:21,370
By this video, you have an overall picture of the service services.