Identify cloud deployment and service models

- When we're using cloud technologies, it's important to understand the deployment models, their characteristics, and what services are available. Join us as we discuss that right now. - [Announcer] You are watching ITProTV. (upbeat music) - Hello ladies and gentlemen. Thank you for tuning into more of the CompTIA Cloud+. That's right, in this episode, we're going to go ahead and we're going to open up the hood. We're going to take a little bit deeper dive on what the engine is doing down there, and what I'm talking about is when it comes to deployment models. In the previous episode, one of the things that we discussed were just some of the high level concepts, but we're going to take a little bit deeper of a dive and look at that as well, as some of the service model offerings we have. Ronnie, you know, I know that we've identified what types of deployments there are out there, but one of the things that we really didn't discuss too much in depth is what each one of those deployment models brings for us. What do they allow us? Where are the resources going to be housed? Who is responsible for what? And we're going to look at that. Where do we get started? - All right, so let's go ahead and kind of start with just a brief review, and then we'll kind of take each one and compare and contrast them to the ones that we need. So on the screen, I've gone ahead and I've pulled up what we've already talked about previously, which is really a basic definition of what these things actually do. Use some of the terminology that I want to make sure that you associate with the particular type of deployment model itself. Now, when it comes down to it, the easiest way for us to understand these is to kind of compare them a little bit more side by side in what they do. So when it comes down to public cloud, Wes, we talked in the beginning about multi-tenancy, so I'm not going to go over that one again, but just remember, here as that review, we can actually both be sharing the same physical server. Your account's going to be different than mine. That makes us tenants, just like if we were in an apartment building together that you actually had your apartment and I had mine, okay? But it's available in the very general public. But let's talk about the idea here of what the public cloud really means for us, the people that are actually going to end up using it, right? It means that we're the ones that really own access to those resources. We also will manage those resources, and we'll operate the utilization of those resources as well. That means we are really responsible. Even though they provide the infrastructure for us, Wes, it's still us that's really responsible for ensuring that in the cloud itself that what we're getting is we're essentially getting a set of the requirements that are actually there, but then we can provision them however we want to, and we're responsible for all that that actually comes in. Now, when we compare that to the idea of the private cloud, remember we talked about the idea of the cloud within the cloud, this normally belongs to a single organization. And yet notice that the way that we actually do this, it kind of sounds exactly the same here, okay? Now the difference here though, Wes, when we start doing something like this in terms of a public cloud, is that with a private cloud, we normally can be the ones that are actually totally responsible for everything we see right here. But Wes, this is another neat thing about private cloud environments. We can even offload that responsibility to, let's say, a managed service provider, okay? In other words, we can get somebody else to manage all this for us and that they have the ability to manipulate to do all the things that we actually need them to do by us just simply calling them, say, "Hey, we need this to actually go up and we can actually do that as well." But this time, they have the resources and they have the command, they have the wherewithal or they have the actual ability to continue to spend a little bit more money if they need to to change those as they need it. So private cloud is that way, okay, for us. So that's how we can compare that one. All right, comparatively here, don't forget in terms of the hybrid cloud though. The key here is central management regardless of where the resources actually end up lying. And this can actually be done in a couple of different ways. This is normally going to be because that single organization that also have a specific set of requirements that they may not be able to meet with just a private cloud or a public cloud or even a community cloud, but they need a mix of all those possibilities there that they might have some services that are actually just in the general public. Let's say, for example, the idea here of a web front end that we have, but our database may actually be inside of a private cloud resource. We may have our backups running, which this would be silly, but I'm just using this as an example, we could have our backups running on premises instead. So we might even use more than one when we actually do something like this. But there's a set of requirements that we tend to have to follow to be able to actually do what we actually want them to do. Now, here it is that combination of two or more deployment models, but this time, when we start talking about hybrid models here and even sometimes in the public cloud, we don't know exactly where those resources end up residing. So that's kind of one of the things that you're not exactly sure. When you tend to access them through that central management of them, you go, "I'm going to access this particular file or this folder that I have access to." Wes, that folder could actually be residing on your on-premises cloud that you have or could actually be in the cloud itself. The user has no clue whether it's here or whether it's actually up there in the cloud. So we don't exactly know, and that's all transparent. Sometimes you hear the term abstracted from the actual user to actually bring this in. Then, of course, there's a community cloud. Single organization or the entire community has access to it. But we don't tend to let it completely open to the entire public itself. You may have where your organization is so big, okay, that you go, "No, I actually need to make sure that I follow all the requirements in that community." But at the same time you may go, "I don't want the rest of the community to be involved in it." If you're willing to pay for it, you know, who cares? So that's what it comes down to. For the differentiation here, of course, is compliance or regulations when we start doing this. So Wes, when we actually kind of take a look at the comparisons here, this is not the deepest dive into each one of these. And the reason why, Wes, is we kind of mentioned in a previous episode that when we start talking about these deployments, everybody kind of does them a little bit differently in terms of how they describe them, how they actually do this. This is the most generic way that I can actually find when we start trying to identify each one and you start comparing them side by side here. It actually hopefully makes a little bit of sense of the responsibility that's actually out there, as well as who tends to use it too. So Wes, this is kind of a little bit more of a deeper dive in that way. - Sure, and, you know, in the last episode, one of the things we kind of seen and we got a higher level overview is this responsibility, right, 'cause when it comes to the various services that are out there that you're going to be utilizing it, believe it or not, in some of those services, we can't say what's all the cloud provider that's going to be responsible. And it's important to be able to identify do you have some of the responsibility for configuration, setup, and maintenance, or does the cloud service provider have that? So can we talk a little bit about that when we talk about that shared responsibility model? - Sure, so in that previous episode, we had mentioned the idea of pizza as a service to kind of help us to ensure that we actually, you know, was able to make some analogy to this. Some of the things we do, some of the things of course the pizzeria does. So that's something we're not going to go over again. But when it comes down to the shared responsibility, we can remove that first one. Even though I have SaaS up here and you see everything's really what the provider does, we still interact with 'em, you know, with it totally. So I'm still leaving it up there for something that we want to do. When it comes down to infrastructure as a service, remember what's actually happening here is that we are now interacting it as a subscriber into whatever cloud environment that we end up choosing. So that means you set up an account and then you can actually choose what pick or model of service that you're going to get. And that means you also pick, you know, who that provider's going to be. So infrastructure as a service for us is actually where the subscriber himself begins to actually go ahead and carve out the resources for his own compute. Now, that means things like virtual machines that we have. He can also of course begin to end up configuring the networking the way that he needs to and the storage requirements the way that it's actually needed, as well as operating systems and applications that he needs in the cloud. That infrastructure as a service, the only thing that the provider is really providing is the infrastructure, you know, that actually is there, but for the rest of us, right, we're actually getting access to being able to do what we need to. The subscriber doesn't end up managing any of the underlying equipment nor any of the actual infrastructure itself. So when it comes to examples of some of this, these are probably where the two major providers in the world right now, Wes, they had the share of the market. It's going to be where you actually hear about, of course, Amazon AWS and Microsoft Azure. Are there a lot more out there? Absolutely. But those are probably the two biggest providers when it comes down to this. - You know, one of the things, Ronnie, I look at is that software as a service, 'cause it's probably one of the, you know, the service models that whether you are actively pursuing a career in cloud, you're probably used more than you realize. So, for instance, let's take something like Gmail. Let's take the entire Google Suite, right, Google Docs, right? So, for instance, if you think about using Gmail, what operating system is that running on behind the scenes? Now, I know some of you saying, "Well, I've got Windows." Well, you're using a web browser, keep that in mind. But behind the scenes, are they running their infrastructure on Linux machines? Are they running on Windows? When's the last time you had to update those operating systems? When's the last time you had to configure their networks in order to use that kind of software? How about this? When's the last time you've actually had to update Gmail itself? When's the last time you had to run an update on Google Docs, right? You don't, because all of that, and Ronnie's mentioned this before, has been abstracted behind there. All you have to do is subscribe to the application-based service there and you get access to that and they handle that all behind the scenes. So when we talk about those service models, Ronnie, let's go ahead and dive in a little bit more and let's find out, you know, when it comes to the services themselves, what are some of the things that they provide for us and how can we compare and contrast 'em? - Yeah, so remember that there's also platform as a service out there for us. And when we start talking about platform as a service here, this is where the subscriber's going to probably access or create his own type of custom software or third-party apps that he's purchased that he's actually running here. And includes, of course, all use of all the programming languages that you might see, services, libraries, tools that are actually sort of, they're actually going to be supplied by the platform itself. And here, this is where the subscriber doesn't actually control any of the infrastructure at all, but only what he's deployed and configured for that application. So as an example here, I went ahead and created this little kind of table, I guess. Platform as a service, you actually hear things like the idea here of AWS's Elastic Beanstalk. Another one, especially in something like this, is going to be a development platform that you call Cloud Linux is also out there. If you're developing, of course, cloud-based apps, there's also Google App Engine. That is another example of something that we see in terms of platform as a service when we start to actually end up doing this. Now, the first two, Wes, those are probably the, I'm trying to think of the best term for it, the more business oriented where the entire business itself relies on the infrastructure to be in the cloud, because we don't want to have, let's say, a big gigantic server farm right here on premises, right? When pushed everything in the cloud, we're going to use infrastructure as a service. The idea of also having a development team working on custom applications like a web front end or the entirety of the web front end, backend, and everything else, but we want to manage them in the cloud, we're also going to use something like platform as a service. The one that seems to be a little bit more in that kind of area between the business and the consumer here, Wes, is going to be the software as a service, which is the software as a service here. Now, what are we actually providing here, Wes, when it comes down to it? So even though I have here, Wes, the provider provides everything, guess what? They don't provide the money. - (laughs) That's right. - Right? So that means that you provide the money to get access to everything that you see right here. Whereas the other ones, you have to provide a little bit of program. The first one, you have to actually provide the knowledge and knowhow, how to configure, how to do all that stuff. You get everything, but you still have to actually put that in place. Wes, with the idea of software as a service, I don't have to do any of that, okay? So, for instance, any bias used Microsoft 365, Wes, notice they didn't have to go out and they didn't have to install Microsoft Office. They could use it right there if they wanted to. The idea of the email service that's found in Office 365 is also there and available. If I wanted to use the web, the Microsoft Word or Excel that's actually right there, all that's actually available in the cloud. Wes, I didn't have to actually set up anything like that as far as servers or even the apps. If I didn't want to, I could use 'em all right there. Same thing with something like GitHub. If you want to store your code, you can actually do all that and they'll handle all that for you. Shopify is a big one. You want to set up 'cause you're selling something that you actually have on the side there. You can create an account there and begin to actually set up your own shop where you can start taking orders and getting paid for them too. And by far, the 800 pound gorilla in terms of everything that there is in the internet and times of online sales, Salesforce. That thing is just monstrously big because they're so good at what they do. They've kind of cornered the entire market here. Those are examples of software as a service too. Now, Wes, we're pointing all this stuff out, okay? There really isn't any call out when it comes down to the CompTIA objectives about these particular types of services. So Wes, we're actually doing this because this is probably what they're going to run into, right? - Yeah, it's the most popular when you talk about just the platforms themselves, and I don't mean platform as a service, but when we talk about cloud-based providers, you have three and I will say really two and that's always going to be Microsoft's Azure, that's going to be Amazon's AWS. And then finally coming up slowly is going to be Google's Cloud Compute. So if any platforms that you're going to use, definitely pay attention to those too. First of all, Amazon has been doing this longer than any of the other ones, right? However, remember what Ronnie said about dumping money. Microsoft has dumped billions of dollars into their infrastructure to bring it up and compete, and today they are competing for sure. - Yeah, it's important that even though this is not really part of the exam objectives in terms of actually being able to name any of this, so don't worry about memorizing them for the exam. When you get out in the field, if you don't know what Amazon AWS is, okay, if you don't know what Microsoft Azure is, and you got the Cloud+ certification, you're going to sound a little bit silly. So you should become familiar with these. If nothing else, create a free account and poke around in them. Take a look at actually what is available out there. Also, there's another grouping that we can use here too, Wes, okay? So I already said like for businesses, right, infrastructure as a service is probably where businesses will go to create the machines that they need to, to make sure they have storage provisions to do everything that they need. Developers are who tend to use more often than not platform as a service because it provides all the elements that they need and they can just focus in on the coding. Whereas they don't have to worry about spinning up another virtual machine, they don't have to worry about creating all this other stuff. They can simply use it that way. And then everybody and their mother actually uses software as a service at some point. Whether it's something like this that I actually mentioned here or other things that you use online to get access to, you're probably doing it. And Wes, believe it or not, ITProTV is kind of more of that idea of software as a service because that's what we're actually providing, is software interface for you to be able to gain access, of course, to the ITProTV courses that we actually have right here as well. So hopefully understanding the idea of the cloud services that are actually available, as well as deployment models just a little bit deeper. Can we go much deeper into this? Absolutely. But at this point, you should be able to identify those, be able to also associate those with some of these different models, not so much for the exam, but for real life practical use that you also have in the networks too. So Wes, I think that's a good place for us to end this episode too. - All right, sounds good. Ladies and gentlemen be able to identify those, the differences and the characteristics associated with the deployment and the service models, given a scenario that's going to help you out tremendously. That's all the time we have for this episode, ladies and gentlemen, but stay tuned because as we continue through the CompTIA Cloud+, we've got a lot more exciting topics to talk about. Stay tuned. - [Announcer] Thank you for watching ITProTV.