Now just like there are three different types of cloud infrastructures, we're
going to be looking at
three different types of service models that those cloud infrastructures can
use. Perutations.
Sorry, the math nerd may stick it out, but we're going to be taking a look at
software as a service,
platform as a service, and infrastructure as a service to kind of tie
everything up altogether
and how they work between the public, private, and hybrid or community cloud
infrastructures.
And if we take a look at software as a service first, this is software WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And if we take a look at software as a service first, this is software
applications delivered
over the internet and it accessed usually through a web browser. Think of this
as like office
365 or Gmail or something along those lines. Easily accessible from home over a
web browser
and over the internet and usually works very well with a public based cloud
infrastructure
environment because you can access it nearly anywhere in the world. It's a
little bit more
difficult on the private side because it's a private infrastructure and as we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
difficult on the private side because it's a private infrastructure and as we
talked about
earlier when we were going over private cloud environments, you would need some
sort of dedicated
communication link between point A and point B to be able to get inside of that
private cloud.
And then in hybrid, you would be connecting to the public side and then travers
ing through
those dedicated links to be able to get to the hybrid or community
infrastructure.
But this allows us the software as a service allows us to be able to manage
user accounts,
the secure application data, and it's your proper configuration of service WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
the secure application data, and it's your proper configuration of service
settings
on the service side of the house, basically where we're configured everything
behind the scenes
in that cloud environment to make sure that services like office 365 are
accessible and through
user permissions available to those users. So keep them within that CAH Triad
Confidentiality Integrity and Availability. And this isn't just limited to SMTP WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Confidentiality Integrity and Availability. And this isn't just limited to SMTP
or email.
It's also for things like the Google workspace and whatever else may be out
there. So you could
definitely set this up as a AWS if you want to use that third party service out
there or Microsoft
Azure and set up an environment where users can conduct transactions or be able
to view different
products or conduct shared workspaces over that software as a service because
we're not actually
dealing with the program or operating system or anything on the end user side. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
dealing with the program or operating system or anything on the end user side.
It's just making it
as easy and available as possible. This moves us on to platform as a service
and you may notice a
trending theme here of we're getting nidier and grittier closer to the actual
barebone systems.
See, platform as a service offers us a platform to be able to develop, run, and
manage applications
without having to deal with things like operating systems or security patches.
And this is
primarily done commercially available to the public over the internet as well, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
primarily done commercially available to the public over the internet as well,
but we're not
using the web browser. We're using things like Google app engine, Microsoft
Azure app services,
and whatever the case may be to be able to help us develop those programs that
run as a software
as a service environment for those users connecting through generally a web
browser. But using platform
as a service allows us to protect our application code from users on the
outside and manage access
controls and secure the development and deployment of those different
environments inside of that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
environments inside of that
platform. So we're able to develop different applications that are accessible
as a software as a
service without releasing the code or making the program available to the
general public. It's housed
in a cloud environment and is accessible through those different resources. Now
, I mentioned resources
because we need to be able to move on and allocate more memory, more services
are excuse me, more
processing, more storage, just in case the app that we develop that runs as a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
processing, more storage, just in case the app that we develop that runs as a
platform as a service
gets overburdened allows us to be able to on the fly add more resources and
that's moving down into
infrastructure as a service. Now, once we get into infrastructure as a service,
we're talking about
providing virtualized computing resources that very same memories, same storage
and same processing
power. We just mentioned that we may need for our platform that runs our
software. See, Daisy
Chained along and all that great stuff. But we're basically taking a virtual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Chained along and all that great stuff. But we're basically taking a virtual
ized environment and
making it accessible to those on the internet. So in terms of being able to
access that
infrastructure, this will be something like ESXi inside the VMWare world or
going down to the nuts and
bolts of Amazon Web Service and Microsoft Azure virtual machines like Hyper-V
platform type stuff
and being able to go through and allocate said resources, issue out those
virtual machines that
will run that platform or run that service or server to run that service. And WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
will run that platform or run that service or server to run that service. And
this allows us to be
able to get more detailed on that actual security because we're at the virtual
machine slash operating
system level and we can manage the network security that is within that virtual
ized environment.
Just in case we want to be able to limit, let's say apply a access control list
or a web application,
firewall and protect data stored within side of that cloud environment, whether WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
firewall and protect data stored within side of that cloud environment, whether
it be a public
private or hybrid slash community cloud. And infrastructure as a service is
generally going to be at a
very bare bone, just about as bare bone as you can get level when it comes to
working with things
on the cloud because you're going to need to access directly to those systems
to be able to install
virtual machines or modify said virtual machines. Now it could be that you are
in some sort of
environment to where you are allocated, you log in through ESXi or through the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
environment to where you are allocated, you log in through ESXi or through the
Azure virtual
machine management console and you go in and you're allowed to play within a
certain resource
pool that's already pre-allocated to you. But you're actually working on those
physical systems
that are all tied together inside of that cloud environment to be able to build
out that platform
as a service.