WEBVTT

00:00:01.040 --> 00:00:05.360
Let's look a little more in depth at the various cloud service models.

00:00:06.440 --> 00:00:10.760
Software as a Service is something we're all really very familiar with

00:00:11.140 --> 00:00:17.080
where, for example, a consumer uses applications provided on and running on

00:00:17.080 --> 00:00:20.770
the cloud service provider's cloud infrastructure.

00:00:21.240 --> 00:00:24.590
The cloud service provider manages the application,

00:00:24.600 --> 00:00:31.160
say, email or some type of streaming for some type of media.

00:00:31.540 --> 00:00:36.570
And the consumer accesses the application through a thin client, say, a

00:00:36.570 --> 00:00:40.780
browser or some type of application program interface.

00:00:41.540 --> 00:00:45.450
The consumer may actually manage access for their users.

00:00:45.630 --> 00:00:48.900
If I have an account to watch some type of streaming,

00:00:48.900 --> 00:00:52.510
for example, shows on television,

00:00:52.570 --> 00:00:57.980
I may be able to share that or have a family joint account for access.

00:00:57.980 --> 00:01:03.520
In Software as a Service, we see here that the areas that are the

00:01:03.520 --> 00:01:08.280
responsibility of then the Software as a Service cloud service provider

00:01:08.280 --> 00:01:11.540
is then the actual presentation.

00:01:11.550 --> 00:01:17.830
How would they then interface with the user? And the platform

00:01:17.830 --> 00:01:21.870
used for that, the application program interfaces to access

00:01:21.870 --> 00:01:25.790
things like their databases underneath the application. And of

00:01:25.790 --> 00:01:30.870
course, they manage the data, metadata, and content that is available.

00:01:31.540 --> 00:01:36.800
We can see then that this runs on top of a Platform as a Service, which, in

00:01:36.800 --> 00:01:41.110
fact, also then runs on top of Infrastructure as a Service.

00:01:42.350 --> 00:01:46.250
The division of responsibilities in Software as a Service

00:01:46.260 --> 00:01:49.770
is as we looked at earlier in this course. The cloud

00:01:49.770 --> 00:01:54.860
provider manages the application, patching it, and so on, such as mail.

00:01:55.410 --> 00:01:59.580
They then, of course, also have total control and ownership of the

00:01:59.580 --> 00:02:03.260
middleware, operating system, hardware, and even the facility.

00:02:04.040 --> 00:02:09.270
The cloud consumer really has no control over where their data is stored or

00:02:09.270 --> 00:02:13.990
processed, and very limited admin control say, for example, just things like

00:02:14.000 --> 00:02:20.010
user access. When we look at Platform as a Service, this is where the consumer

00:02:20.010 --> 00:02:25.860
can deploy customer created or acquired applications on the cloud service

00:02:25.860 --> 00:02:27.790
provider's cloud infrastructure.

00:02:28.400 --> 00:02:33.760
The cloud service provider provides library, services, tools, languages.

00:02:34.240 --> 00:02:35.550
So say, for example,

00:02:35.550 --> 00:02:39.960
I bought an application that I want to use, a finance application.

00:02:40.540 --> 00:02:43.650
I could go to a cloud service provider and say I'd like to

00:02:43.650 --> 00:02:46.600
run my application on your platform.

00:02:47.040 --> 00:02:50.320
And the cloud service provider would then provide the

00:02:50.320 --> 00:02:54.240
infrastructure for my application to run on the servers and

00:02:54.270 --> 00:02:57.060
very often even databases and so on.

00:02:57.940 --> 00:03:02.850
And the cloud service provider manages that underlying infrastructure

00:03:02.850 --> 00:03:07.130
while the consumer has to manage their application, which would include

00:03:07.130 --> 00:03:10.150
things like patching their application and so on.

00:03:11.740 --> 00:03:15.830
If we look at this, now we see that the responsibility of the cloud

00:03:15.830 --> 00:03:21.290
service provider is the element of infrastructure service, but on top of

00:03:21.290 --> 00:03:26.830
that, the integration of middleware necessary for the application that the

00:03:26.830 --> 00:03:29.460
consumer has purchased then to run on.

00:03:30.440 --> 00:03:34.530
In this case, the cloud service provider has no control over the application.

00:03:34.590 --> 00:03:36.990
It's being managed by the consumer.

00:03:37.100 --> 00:03:38.160
They do the patching.

00:03:38.610 --> 00:03:43.350
They still have admin control over middleware and total

00:03:43.350 --> 00:03:45.860
control over the physical facility.

00:03:46.440 --> 00:03:52.060
The cloud consumer has real control then over the application,

00:03:52.440 --> 00:03:56.280
the installation, patching, and so on, access controls.

00:03:56.290 --> 00:04:03.060
And they also then have to manage their interfaces between their program and the

00:04:03.060 --> 00:04:08.440
underlying infrastructure. In Infrastructure as a Service,

00:04:08.850 --> 00:04:13.480
the cloud service provider provides the building, the underlying infrastructure,

00:04:13.860 --> 00:04:17.959
but the consumer manages operating systems, storage,

00:04:17.970 --> 00:04:22.160
applications, and perhaps even some network components at times.

00:04:22.940 --> 00:04:26.970
And in this case, of course, we said we could have a off‑site

00:04:26.970 --> 00:04:30.000
private cloud be a very good example of this.

00:04:30.940 --> 00:04:35.930
So the cloud service provider manages the facilities, hardware.

00:04:36.110 --> 00:04:40.950
They manage the interface down to the hardware through some

00:04:40.950 --> 00:04:44.300
type of abstraction, and they deal with,

00:04:44.300 --> 00:04:46.530
of course, network connectivity.

00:04:46.540 --> 00:04:51.950
And then there are the APIs, which become the interface between the

00:04:51.950 --> 00:04:55.460
consumer and the cloud service providers areas.

00:04:56.740 --> 00:05:01.750
In this case, the cloud service provider has total control over hardware.

00:05:02.310 --> 00:05:05.320
They have admin control over the hypervisor,

00:05:05.320 --> 00:05:08.580
but we can see here the cloud consumer has to be able

00:05:08.580 --> 00:05:10.360
to interface with that as well.

00:05:10.840 --> 00:05:17.420
And total control of the application middleware and guest operating system has

00:05:17.420 --> 00:05:21.250
now passed from the cloud provider to the cloud consumer.
