When we look at the various cloud deployments,
we've seen, for example, and discussed a little bit about a private cloud,
which quite simply is a cloud or a set of IT infrastructure which is
provisioned for the exclusive use of one organization,
and many companies have done this.
Yes, they're using cloud‑based services,
but they are the only tenant, it's not a multi‑tenant environment.
This could either be in their own facility,
their own server room, or off‑premise as we've discussed as well.
In many cases,
the private cloud could be owned by the organization
itself or it could actually be owned, managed,
and operated by a third‑party where the third‑party actually does all of
the support work to ensure that this operates correctly.
The organization that is the cloud consumer then
doesn't have to worry about their IT, they've outsourced all of that.
When we look at an outsourced private cloud scenario,
for example,
we can see on the right‑hand column here the customers
facility where they have their own users,
and within their trusted computing base,
their security perimeter, and they manage things within there,
the things like the endpoints and user access levels.
But within the facility of the cloud provider is a separated area which
is very often physically isolated from the other parts of the cloud
service provider's service offerings and it becomes a separate domain
within that cloud providers facility,
and it is there for the exclusive use of that consumer
organization with its own perimeters, its own access controls,
and so on.
We also, of course, have the most common,
the public cloud,
something that almost everybody uses today, where we have a cloud
infrastructure which is provisioned for open use by the general public,
email services and so on.
This exists on a premises of the cloud provider,
and in fact, in most cases,
the cloud consumer has no idea where their data is actually being kept.
They don't know whether email physically is located or all of those
pictures that were backed up off of their phone,
for example.
We also, of course, have where several organizations work together.
This is a community cloud, and this has been done by universities,
it's been done by hospitals, it's been done by government.
The idea is that you have a cloud infrastructure which is provisioned,
but only for a select group of organizations,
maybe a specific community of consumers that very often
have the same types of requirements.
Two or three universities or two or three hospitals,
for example, go together,
and instead of each having their own separate data center,
they have one shared data center because all three hospitals
really have the same regulatory needs, the same types of policies,
and so on.
So therefore, a community cloud can operate for one of the universities,
maybe it's even an onsite private private cloud,
but for the other two universities or other two hospitals,
it's an offsite private cloud, but it's,
it's a community, the three of them work together,
and of course,
there are the advantages of the resource pooling
and economies of scale and so on.
Now it could well be that I gave you the example that of the three hospitals,
one of them hosts the data center,
but we also see other cases where that community was hosted by a
third‑party cloud service provider as well.
And of course,
this could be either on the premises of one of the
universities or hospitals or off‑premise altogether.
The idea of an outsourced community cloud.
We see that we have a number of different organizations that
are similar on the right‑hand side here,
community organizations, consuming cloud resources,
each one has its own security perimeter,
its own trusted area that it communicates through some type
of access controls to the community cloud,
which in this case,
we're showing hosted as a cloud provider's facility that really operates,
as we said, almost like a private cloud,
except for the fact is for say, three companies in this case,
but within that cloud providers facility.
We also have the hybrid,
which quite simply means we're not satisfied with any one of these,
we use a combination.
So a hybrid cloud is a composition of two or more distinct cloud
infrastructures that operate as separate entities,
but are bound together by standardized or proprietary technology.
So this could be for the sake of business continuity,
it could be, of course,
that we have a couple of different infrastructures that operate and cooperate.
We could say that even though they're separate entities,
it's seamless often to the cloud consumer because the data can pass
back and forth between them without any restrictions.
So this allows what we called before cloud bursting where I
can easily move some of my processing off to another
facility and that's what we would, therefore,
also therefore call data portability.
We see here in a hybrid where we could have a
combination of almost any of these, a combination of an onsite private cloud,
an outsourced private cloud, an onsite community cloud,
an outsource community cloud, or the public cloud.
And so a hybrid is, as we said, two or more of these that work together.