Up to this point, we've been covering software as a service, which are
different services that we can access that's generally over a browser and think
of along the lines of like Gmail or even social media to an extent.
Then we went into platform as a service where we were expanding the usage of
actual application modifications and management on our end as far as the
clients responsibility is concerned.
But all the servers and infrastructure that is behind the scenes is still WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But all the servers and infrastructure that is behind the scenes is still
managed by the actual provider broken down into those two areas of
responsibilities that we emphasized from the beginning.
The clients responsibility and the providers responsibility well here we're
moving more into the infrastructure as a service.
Now this is getting very close to just saying you know what we're going to keep
everything in house.
But there is an advantage to infrastructure as a service and with those
advantages also come security concerns which will be covering throughout the
skill. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Because as we move into infrastructure as a service we're going to see that the
responsibilities for the client meaning us vastly expands and the actual burden
on the provider is far less than it's been before up to this point.
Before the most we've had to worry about as far as you know technical abilities
and make sure everything's maintained is the actual people in data and
applications.
Now we're expanding on into taking care of the actual runtime middleware
operating system and virtual network with the provider being responsible for WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
operating system and virtual network with the provider being responsible for
the actual hypervisor server storage and physical network of the overall
infrastructure.
Now you may be thinking that's a lot and where does that line get drawn at
where we actually maintain physical equipment versus actual infrastructure
equipment that's maintained by the provider.
Well I'm glad you asked let's take a small look what we're taking a look at
here is a normal server room environment think of these as different servers
and all the networking components that are in here.
Didn't want to go too far in the detail just kind of give a brief sketch of an WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Didn't want to go too far in the detail just kind of give a brief sketch of an
overview.
And if we maintained everything didn't utilize any client kind of cloud
infrastructure this would be the setup that we would be required to have
somewhere within our organization.
It could be this one it could be multiple of these and being able to maintain
something like this definitely increases the cost not only for the actual
physical equipment but also for the actual maintenance of the equipment and
making sure that the network connections between here and the other sites is WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
making sure that the network connections between here and the other sites is
maintained as well.
So when we go to infrastructure as a service this particular server room as we
have on the screen right now basically turns into a cloud component for us but
we have a lot of control over what goes on in the server room as far as being
able to utilize the storage the memory the processing for our organization.
See in infrastructure as a service there are multiple of these types of setups
all throughout the cloud infrastructure which is why basically this is called WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
all throughout the cloud infrastructure which is why basically this is called
infrastructure as a service when we break down the components of it we're
looking at actually the physical components that were in our diagram being the
responsibility of the provider and the configuration of those components being
our responsibility.
Now there's a kind of a split off here and understanding that we kind of follow
along with for how a virtual infrastructure is built up and I want to have a
link below here to into some of the greater virtual infrastructure courses that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
link below here to into some of the greater virtual infrastructure courses that
we have here on CBT nuggets but know that when we have a server room like this
and we have access for it under that infrastructure as a service there were
actually utilizing the hardware that are at these different sites be it hosted
by let's say Microsoft Azure
AWS there are many different ones out there and when we take a look at what we
're actually allowed to touch we're basically saying we're waiting on you the
provider to install the physical hardware have that hardware back up ever done WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
provider to install the physical hardware have that hardware back up ever done
to see throughout your cloud network so we can load balance we can make sure
that there's consistent access to it and then we'll take care of everything
else as far as the configuration because once that type one or type two virtual
ization is installed on hardware we have
everything else and that includes maintaining things like the virtual network
where we can expand and make different reliance we can go through and create
different operating systems in that virtual environment such as server or work WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
stations we can have dummy clients at the actual locations of our clients and
have them just virtually connected to those operating systems that's in that
cloud infrastructure.
So far is to even house through the point of this entire domain Cisco
environment inside of that infrastructure as a service environment and kind of
do some of the other things that we did in the previous skill where we're
looking at platform as a service more in depth inside of infrastructure as a
service let's go ahead and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
back into our sandbox environment and just take a look at some of the different
services offered and how they would be different from platform to
infrastructure as a service.