All right, let's go ahead and take a look at our cloud deployment models. So when we're talking about
just general basic cloud information, they're usually two pieces that we have to start with. We have to start with how we're gonna deploy the cloud, and then we have to talk about what service is we want from our cloud service provider. So when we're talking about deployment,
we really have four different deployment models. We have a public cloud.
We have a private cloud, we have a hybrid environment, and then we have a community cloud. So most of the time when people say the cloud with their generally referring to is the public cloud.
So ultimately, this is your Amazon, your Microsoft, your Google service. These are your public cloud service providers.
So what that means is anyone can use space on the servers or access. Their resource is. It's open to the public. And when you have a public cloud again, you don't really have control over location of resource is you condone, definitely expect to be in a multi tenant environment.
SoHo Purpose of the public cloud is that public is sharing all of these resource is
so it's the least expensive of the deployment models. But from a security concern, you're gonna have the greatest risk. Really.
Now, um, you know, again, it's a cost benefit. I'm gonna sacrifice security in exchange for calls.
And I'm not saying that public cloud service is certain public cloud service providers can't secure their environment. But again, you can't get rid of some of these risks associated with not having it directly. Control, not having direct control of location
and also of not having control the tenants. You just can't fix that, right? So we might then go to the private cloud and the private cloud says, Look, I like this idea about this Broad networks access. I like this ubiquitous computing. I like the elasticity. I like the convenience,
but I don't want to just turn over control of of all my data
to a server that's gonna have 50 other clients on, right? So I really say that the best way. I think you know what I'm talking about. So what we can do with the private cloud then is devote a set of resource is to a particular client. Like, for instance, the government cloud or,
you know, an individual organization may configure their own private cloud
that offers the same resource is through the through the Internet but just doesn't allow more than 1 10 right? This is mine. These are my resource is it doesn't matter if I host them in house
right? Or if a cloud service provider host that we can still have private cloud on either of those instances, it really is about how much control do I have over the information? Where's it located? How's it protected?
Uh, who has access? So I get a lot more control over Private Cloud.
Flip Side of that is, of course, because I have exclusive use off. The resource is it's more expensive,
but I get a lot more flexibility, and I can you know where this says hi scape ability. And I still have those benefits of the public cloud. And what I can find is that in the middle, you know, maybe I'm paying for a set of resource is on the private cloud.
But once again, that scenario where maybe every September our sales increase, our sales explode.
So all of a sudden I need more resource. Is that I have available to me in the product cloud. Well, we can use. Resource is from the public cloud if we've set up a hybrid environment and sometimes you'll hear the term bursting. So the idea of we have these bursts in needs, then they go away,
burst in the money. That's the whole point of elasticity, and that's a big benefit of a hybrid cloud.
I keep my stuff private mind, mind, mind, mind, mind.
But in the event that we need additional storage Aiken borage some of that storage space, for instance, from a public cloud provider right to hybrids in between public and private. And then the last one. You know, you get a little more expensive than public, little less expensive than private.
You get some benefits there.
Good cost effectiveness. Um,
you know it's right there in the middle
community, quite old. But here's one thing worth mentioning ease of use. Here's a phrase you can migrate gradually phasing in workloads, and that sounds like a good question, doesn't it? I've been taking exam. I might write a question about that
like maybe which deployment model would be best for an organization that wants to slowly transition to the cloud.
Heiberg For now, right? Let's test the waters out. Let's bring in our elements slowly, and then we'll see where our needs go from there. Right, Good test question.
All right. And then the community cloud.
The idea about a community cloud is work one to share Resource is with other organizations that are in the same that have the same requirements. So, for instance, as a health care provider, I have to be hip, A compliant So a cloud service provider might specialize in Cloud based Resource is
four organizations that have to be hip, a compliant,
so hospitals, doctor's offices, clearing houses they may all want to use. Those resource is because we have that sort of understanding of the minimum level of security at the Cloud Service provider being in compliance with Hip. So ultimately it's for organizations that are a little more specialized.
And, uh, you know, the big phrase. There's just gonna be words. We have similar privacy requirements.
All right, so this is just Excuse me, This is just a good chart again. This might be something that I'd screenshot just to give you sort of an idea off water. The key pieces about each of these clouds. Right? So public cloud for public right,
bearable workloads. That's fine. Testing and development. You know, really, this is one that just has a wide span of uses. You know, we could just go on and on. Bess uses of the public clouds. I think just variable were close. Not necessarily test and death, you know, Not necessarily more so than any other resource.
All right. And then the pros and the cons with each again really important to know.
Now, this idea with the private cloud if you go over to challenges and it says high cost of ownership and a required skill set Well, it depends, right? It depends on how much you're off sources, you know? Am I doing this in house? But I'm hosting my own private cloud. I better have a high skill set,
and it's gonna be expensive for me, toe. Oh,
but if I'm leasing a private cloud service from CSP, maybe not so much so again. There few black and whites. And that's one of the things about cloud computing that makes these tests and these exams so difficult is there are no longer the clear cut lines that we've always had in the past,
right? We stored our equipment on Graham,
who was responsible for that equipment. Me, who was responsible for physical breaches me was responsible for data breaches me, who was responsible for liability? Me, who was responsible for blah, blah, blah, blah, blah. Right. But now that we're sharing these surfaces across the network, it becomes much more difficult. So thes air kind of
guidelines. I wouldn't say anything here written in stone, and you can find an exception for just about anything that's documented. But these air just generalizations always think of this is just kind of common knowledge and best practice information. All right, so when you're looking at your cloud deployments summary,
you can see the four pubs, public,
private hybrid and community