Cloud Concepts and Architecture

0:06Today it's time to talk about cloud computing roles. Now, if you've watched wrestling in the past maybe roughly 20 years or so, you may have heard the saying, know your role. Well, even if you haven't watched wrestling, you may have heard that saying. And the thing is, in cloud computing, we've got roles. And the thing is we need to know what those different roles are because those different roles have different responsibilities.

0:37So let's jump in and talk about some of the roles in cloud computing. So we're starting off with the customer. Now, the customer is going to be who's using those cloud services, right? Yeah, we know that. But here's the thing. When it comes to cloud computing, the customer is going to own the data, right? It's the customer who's going to upload the data into the cloud environment. And it's the customer who's going to use the platform as a service to go out and build different applications.

1:10So the customer's using data, right? They're uploading their data into the cloud. They're using and building applications in the cloud. They're using those services. So that is the role of the customer. But what other roles are there? Well, we've got a cloud service auditor. That's a role. And these are folks that are out there verifying that those Cloud Service Providers, those CSPs, are doing what they're supposed to do. They're meeting their Service Level Agreements, or SLAs. So these auditors are actually out there to help the customer, right?

1:43They're out there to help make sure that those CSPs are doing things like they're supposed to and like they say they're doing and again, meeting those service level agreements. And next up is the cloud service broker. Now, this is a person, or actually an organization, that kind of maintains relationships with multiple cloud service providers. So they've got a bunch of CSPs out there that they work with, this cloud service broker over here.

2:14And what they do is they kind of act as a consultant to the customers. Because when a customer is deciding that they want to go into the cloud-- they want to start using cloud services-- they may go to a cloud service broker as a consultant to help them identify which cloud solutions meet our needs or which cloud service providers best fit our organization's needs and requirements. Because this cloud service broker over here is going to be very familiar with all these different CSPs they have relationships with.

2:48And they're going to know about their services and how they do business and all those things. So as a customer, we can rely on a cloud service broker to help us identify what cloud services and cloud service providers might best fit the needs of our organization. And yes, it's true these cloud service brokers do sometimes resell cloud services. And that's just kind of part of their business model. Next up? Well, we can't leave out the cloud service providers, right? Those are the folks out there in the cloud providing the services.

3:19They provide us with the CPU in the cloud, the memory, the storage in the cloud. They provide us with the platforms for our platform as a service, right? They provide us software. That's part of software as a service. And then of course, these up here, if we put that over there, these are part of your infrastructure as a service. And then they provide us with billing as well, right? They're going to bill us. But they also track our usage. And that really is something very important because again, the cloud services, it's kind of a pay-as-you-go method.

3:56And it is a metered service. So you only pay for what you use. That's your usage. That's the meter. And you kind of pay as you go. And your cloud service provider is providing these services to you as the cloud customer. And we got one more to talk about, and that is a cloud service partner. And these are roles that support and work with the CSPs. And these are any roles, such as a cloud service broker that we talked about, or it could be a cloud service auditor.

4:27So those brokers and auditors are kind of in a supporting role. And they help support the CSPs. And they are a cloud service partner. And there we go, cloud service partners. And that is the list of the roles that we need to know about in the cloud. We had our cloud customer. Of course, that was us, using cloud services. Or I guess if you work at a cloud service provider, then that wouldn't be you necessarily. But it's going to be our cloud service auditors, of course, as well.

5:00And then we had the brokers, who brokered services and helped us identify as a customer which services best met our needs, maybe which cloud service providers best met our needs. And of course, we got the providers who provide all those great cloud services and then lastly, our partner. So those are the different roles in cloud services. Hope this has been informative for you, and I'd like to thank you for viewing.

0:06I've got a question for you. What makes you awesome? Is it your sense of humor, is it your leadership abilities, or maybe it's your depth of knowledge in something. But these are all characteristics that you have that make you awesome. Well, cloud services have characteristics as well. And guess what? They make them awesome as well. So let's jump in and talk about some of these cloud characteristics. So here we're talking about cloud computing characteristics and, of course, all those things that make it awesome.

0:37Well, let's start with number one. On-demand self-service. Now this is pretty darn cool. Think about before cloud. If you're not using cloud, then think about today. You want to deploy a new server. Well, what are you going to do? Well, I need to go and I need to get approval to purchase a new server, I need to order that server, and then I need to-- I'm can put dash, dash, dash-- wait for that server to come in. Then, once it does come in, then we're going to go and we're going to unbox it, and we're going to rack it.

1:10We're going to cable it up, then we're going to fire it up. We're going to install our OS. And then we're going to do our patching. And then we're going to do whatever else it is that we need to do to make that server what we want it to be. That is a lot of work. And guess what? It takes a lot of time. Wouldn't it be great if we could just do away with most of this? Well, we can and there's the on-demand self-service. We can log into our cloud console and we can click some radio buttons or widgets in there.

1:41And we define how much memory, how much CPU we need, how much storage we need. We go through this. And within just a couple of minutes, we have a server up and running spinning in our cloud environment. Now you take-- let's say it was five minutes. Five minutes versus maybe five weeks if you're lucky. So that's a big difference and it's on-demand. If you want to make changes, boom, jump in there and make changes. And that is pretty darn awesome when it comes to cloud services-- our on-demand self-service.

2:11We also have global access, which really is the whole idea of using your cloud management console. You can log into that from anywhere in the world, doesn't matter where you are. You're on vacation and you've got an emergency, you've got to jump in and work on it, or maybe you just want to work remotely. A lot of us are doing that these days. And you can manage your environment from anywhere. You have global access, super, darn handy. Think about on-premise. When it's on-premise, how do you manage it? Well, generally, these days, we manage it anyway. We VPN into our environment and then we manage it from there.

2:45But if you didn't have VPN, how are you going to manage it? It can be tricky. Well, we don't have to worry about that with cloud access. It's super, darn easy. Our cloud global access. Next up, resource pooling. Now when it comes to resource pooling, well, we think about this, maybe we've been doing this ourselves. We have all these different resources and we use them as we see fit. Well, in cloud environments when the cloud vendors purchase and set up their environment, they've got all this CPU and memory and storage and network that they've created right.

3:20And they've got these giant pools of resources for all these different things. And what that does is it allows them to use this pool very efficiently. They can fit a lot of customers in these pools of resources. And the idea is they can use large amounts of resources like maybe they operate at 80% capacity. Well, if you think about it, when we have a server on-site, on-premise, and maybe this is an active directory or a file server something, well, we realize if you check your CPU and your resource utilization, in a good day, we're running at 20% utilization probably.

3:59But on average, it might be 15% or 18%. We're not using much, so that's a lot of wasted resources and wasted money too because we paid for this server, but we're only using 20% of its capacity. Well, the thing is, with the cloud providers, they're able to create these pools and efficiently use a large majority of it. So what that does is it makes it more efficient. It allows them to get more bang for their buck.

4:29And then they can pass that savings onto the cloud customers. And why would they want to do that? Because if they can make cloud more attractive price-wise, then on--premise, well, why wouldn't you go to the cloud? It just makes more sense. So that is our resource pooling. Next up, resource elasticity. Now this is awesome. I love this about cloud. And here's the thing. When we have our on-premise servers, we have a set amount of resources.

5:00We deploy our servers over here and we have a set amount of CPU, memory storage-- put storage-- and networking. We only have what we have. It's not like we can instantly get more. We can always go down, but we can't go up, necessarily. Well, in the cloud, ha-ha, we can go up and we can go back down. So think about this. If you're running a web server out here-- there we go-- and it hosts an application that people use, but certain times of the day, it gets absolutely hammered and it gets slow.

5:36Wouldn't it be great if we could add more resources to it or maybe a second instance of that server, but only during certain periods of the day? And then during the off periods when we're not real busy, well, we could actually just get rid of that extra server or resources. Well, guess what? We can do that in the cloud and it is resource elasticity. So during peak periods of the day up here, we can increase our resources.

6:07And then during our low demand periods, well, we decrease our resources. And this could be automated. But why do that? Well, here's why. Let's jump over here and see why resource elasticity is so awesome. Because cloud is a measured service. You pay for what you use. So what that means is if you can only pay for a lot of resources during peak periods and a little bit of resources during your downtimes, well, wouldn't that be great? It's very efficient dollar-wise.

6:39We're not wasting money on resources we're not using. And that's why resource elasticity really can save us some money and help us meet the demands of our customers. And that's pretty darn awesome. Now, again, yes, measured service. We're only paying for what we use. So think about this. On-premise, when we buy those servers and deploy them, maybe we're using 30% of the resources on those servers. Well, we're still paying for 100% of those servers that we bought and staged and racked and got ready to roll and are managing.

7:14But we're only using 30% of their ability. Well, that's not cool. Well, that's the thing with measured service, we only pay for what we use. So we would only be paying for our 30% that we're using. And that is super awesome because now we're not wasting resources. And, yes, money is a resource. So there you go. Those are some cloud computing characteristics. We had our on-demand self-service, global access, resource pooling, resource elasticity, and measured service.

7:46And, yes, they do provide us benefits. They help us to only pay for what we use and adjust what we're using to meet demand and access and manage it from anywhere, and make changes on a whim. So those are some characteristics that make cloud computing awesome. I hope this has been informative for you, and I'd like to thank you for viewing.

0:00[MUSIC PLAYING] When you go shopping for a vehicle. Well, you've got different models to choose from. You have got sedans, and coupes, and trucks, and SUVs. All these different types of models to choose from. And the same is true for cloud. There are different models of the cloud. So let's jump in, and talk about some of these different models, and some reasons that you would choose one over another.

0:31So our cloud deployment models that's what we're talking about here. We've got private, public, community, and hybrid. Those are four different cloud deployment models. So let's take a closer look at each of them. Starting off with private. So the private cloud is private. . It's used by a single organization. So this means that only one client is housed within this cloud here. And this cloud could be managed by the client themselves, or it could be managed by a cloud service provider.

1:06So it could go either way. The client managing it, or the cloud service provider. Now, what are some benefits of a private cloud? Well, some benefits would be increased control over the data, and its underlying systems. Definitely retaining of ownership of the data, because if you don't have any other clients, where you could have some cross-contamination of data, or you're going to have a better chance of retaining your ownership. You also have the ability to add additional governance of controls.

1:41And that's because in another type of cloud, the public cloud, where you have lots of different customers in it, you might not be able to make changes or have the CSP make changes for you, because it would affect other clients. But here we could actually have additional controls over the governance, and maybe add additional security controls. And we also have additional assurance of data location. Because if we have a single cloud, where we are the single client in that cloud, we know where it resides.

2:13And we're going to talk about this as the course goes on, the importance of knowing your data's location. It comes in very handy, especially for legal and compliance requirements. And then lastly, probably the biggest one is privacy. And that's because if you are the only customer in this cloud, well guess what? It's all yours. You have all the privacy. So that is a private cloud. Now, guess what? [LAUGHS] Yes of course, private clouds cost more. Because you are shouldering all those expenses of that cloud yourself.

2:49Or your organization is at least. So keep that in mind. Now, what about the public cloud? The public cloud is a lot different than a private cloud. Anybody can sign up and use it. So that is anybody, including bad guys. And yes, it is possible. And they do, they sign up and they use cloud services to launch attacks, and do things. And yes CSPs or cloud service providers are out there looking for them, so that they can knock them offline and revoke their cloud services, but they are out there so anybody can use it.

3:24And this is your standard cloud service that you think about. When you think about AWS, and Google Cloud, and Azure, generally you're thinking about a public cloud. When you go sign up for an account, and you spin up resources in the cloud, well, that's a public cloud. And your data is isolated between customers, so that other customers can't access your data, and you do have the isolation. But you are sharing the underlying resources. And that's why it's a public cloud. Now, some of the benefits of the public cloud are ease of use.

4:02Because it is very easy to use. You sign up for an account, you log in to your cloud dashboard, and you can start spinning up instances, or using the platform to build applications, or whatever it might be. And user data is isolated. And that's very important, because when you have lots of people using the same service of course, we want to make sure that our data is isolated from each other. So that client A can't access client C's data over here, that would be a bad thing.

4:32And that is a benefit of the public cloud. Also with the public cloud, well guess what? In comparison to a private cloud it's a reduced cost. Because you're not shouldering the expenses for the entire cloud setup on your own. This is a shared endeavor, with all those other users out there. Next up is our community cloud, and this is a pretty interesting one. And it's kind of a cross between a private cloud, and a public cloud. And here's why I say that. You have multiple users like a public cloud.

5:05However, you all share the same need for a specific service, or something. So you're all kind of working towards the same goal. You're different organizations yes, but you all have the same goals when it comes to the cloud. So here's the community cloud It's used by a group of users that we see down here. And they all share the same need, they share the same cloud service, and cost. So the thing is there is a shared need here, and then you all shoulder that costs together.

5:37So it helps to drive the cost down, which is a good thing. Now, the example I'd like to use with this, is because I've set this up for this exact scenario, is a group of doctors. So you've got these doctors offices over here, let's say we've got three of them. And they all share, or they want to start using the same electronic medical record system. And the thing is, these EMRs, these electronic medical systems are pretty darn expensive. And if you spin up an individual instance for each of these offices, well then all of them are paying a lot of money.

6:14Wouldn't it be great if we could spin up one instance somewhere? I don't know, maybe in the cloud. And they could all share that instance. Well, guess what? You can. And that is a perfect example of a community cloud. These folks all want to share the same resource, and it helps to drive down the cost of that resource. So some of the things that you get, some of the benefits of community cloud, are high availability, and resiliency, that's HA, and resiliency that you get with cloud services.

6:49Basically redundancy, and things that the provider has. They have redundant hardware, and redundant networking. And all the stuff that if I was to set this up in a doctor's office, they're not going to have all that stuff. But if we spin that up in the cloud. Yes, they are going to have that. So that's where we come up with a benefit of high availability, and resiliency. We also have a benefit of added security. Because many of the cloud service providers are compliant with lots of different things like HIPAA, and PCI, and SOC, and NIST.

7:22All things that we're going to talk about in time. There is a reduced cost of course, because they're sharing the cost of this. Instead of spending it up on their own individually, they get to share the cost, which is super cool. And then lastly, flexibility. And I say flexibility because if we buy a server and spin it up on premise, in one of the doctor's offices, and we need more memory, or more CPU, or more storage, well we have limitations. A server that we purchase can only have so many CPUs in it.

7:55It can only hold so much memory. It can only hold so much storage. You see where we're limited here. But in the cloud, I can just add, and I can add, and I can add, and I can add, and yes there are limits of course, there's limits with anything. But they're pretty out there. You can add a ton of resources. And you can do it pretty darn quick, with just a couple of clicks, and you've got these added resources. Completely different than on premise. So this is a community cloud.

8:27And we've got one more, and that is a hybrid cloud. And really it's just a combination of any of the other. So if you take a public, or a private, or a community cloud, and you combine them. Well then you have hybrid right. Pretty darn straightforward. Now some of the benefits of hybrids include, hardware it's our HW reuse. And that might sound crazy to you. You think in the cloud it's often some far off data center.

8:58How can I use my hardware in that data center? Well, here's the thing. When you have cloud, you could have a private cloud let's say on premise if you wanted to. Because a cloud is just a group of services, and you might have an on prem, put here on prem. Little cloud that you set up. So it's your cloud, and you're managing it. It is a private cloud let's say. And really what I'm referring to, this is your environment, you're managing it and it is private.

9:31But if you take that, and you connect it to the public cloud where you have an account, and you spin up some resources out there. And you set up a VPN between these two, guess what you've done? You've created a hybrid cloud. You have your private on premise type of cloud, and you have just combine that with your public cloud account. And there you go. So that it is hardware rees where you can use some of your local hardware, in your hybrid cloud. Now, another great piece of a hybrid cloud, is using the cloud for disaster recovery purposes.

10:09Let's go back to your private on prem cloud. Well, wouldn't it be great if you replicated that data up to a public cloud account, and you use it for disaster recovery? Well, you could do that. And that is a hybrid, because you're combining your private on prem cloud, with a public cloud account there you go. One of the other things you might want to do is look at reduce cost by combining your on prem private cloud, with a public cloud account again.

10:42But this time what you're doing, is you're taking the things that you can put in the public cloud that are very little resources. Maybe something new you're spinning up instead of going and spending a bunch of money on new servers, well you just spend it up in the cloud, and your connected to. There you go. That's another example of a benefit. Now, here's the thing. I don't want you to think that a private cloud has to be on premise, because by no means does it have to be. You can have a private cloud in a data center in your same town, that somebody owns.

11:14And they set up some hardware for you, kind of like a co-location, and that's your private cloud there. Or you could have a private cloud, on premise, or you could go to one of the big dogs. One of the AWS, or a Azure, or GCP, and you could talk to them about private cloud. Where they're going to set up your own hardware, your own environment. But it's going to be very expensive I'll tell you that. But there you go. You can have private cloud anywhere. I just don't want you to think that you have to have it on Premise, because you definitely do not. So those are some different cloud deployment models.

11:45But I also said we're going to talk about choosing one, and what kind of requirements drives your choice. So choosing a model. Well, when you're choosing a cloud deployment model, it needs to be based on a couple of different things. Number one is your business strategy. Whatever your business strategy is, you need to take that into consideration. Are you trying to go global? Are you staying local? Because if you're going global, then then the cloud would be the way to go. Because you're going to want to put your resources in multiple locations around the globe possibly.

12:18Well, and something else to consider is your compliance needs, or any type of regulatory needs that you might have, you need to know those. So when you go looking for a cloud service provider, you can make sure that CSP, that Cloud Service Provider is going to help you meet those needs. And of course cost. [LAUGHS] We can't forget cost. Cost always comes into play. What about our risk appetite? Let's talk about that for a minute. Your risk appetite is how much risk your organization is willing to accept.

12:52So when you're talking about risk appetite, if you have very sensitive information, well putting that in a public cloud does have some risks associated with it. And it might be too much risk. You may decide to go with a private cloud because of your sensitive information. And then lastly, any legal obligations you may have. And this could be contractual, or it could be due to regulatory requirements that you are not able to put certain data in certain places, or certain data cannot leave the country.

13:24Those are all things to consider, and that goes back to understanding where your data is located. We talked about that briefly, we're going to talk about it more later on don't worry. But these are some of the things that will help us decide, which of these cloud deployment models is right for us. I hope this has been informative for you, I'd like to thank you for viewing.

0:06When it comes to cloud, there are three main types of services, and we're going to talk about those three types over the next three videos. In this video, we're going to talk about infrastructure as a service. The key word here is infrastructure, and it is the most similar of the three different types to your standard on-premise servers and networking. So let's jump in and talk about infrastructure as a service. So here we are, IaaS, infrastructure service, what the heck is it? Well, as I said, this is the most similar of the cloud Services to your on premise network and server architecture.

0:43And this is where the customer can log in to their cloud service portal and they can go ahead and they can provision their own processing, storage, and networking capabilities. So basically here you're building a network infrastructure in the cloud. So what you're doing is you're building out your network. So you're setting it subnets in the cloud, you're going to be setting up your routing in the cloud, you're going to set up your security groups, and these are your access control lists for your security for network-based accessing certain subnets and port can and cannot communicate to different subnets.

1:26You're going to be spinning up servers, and the servers of course include your CPU, your memory, your storage, and your operating system. You're also going to be dealing with public IPs, and, of course, private IPs, and then, of course, at that point you've got NAT that's involved. So these are all things that we deal with on premise, except here we're doing it in the cloud. Now, some of the benefits of using the cloud IaaS over an on premise is your scalability.

2:05Because you can scale very fast. You don't have to go buy new servers and rack them, we've talked about that, you can just go add more storage or CPU or memory or additional servers as needed. And that also leads to on-demand service, because we can do it on demand, we just log in and do it. Super cool, and it is a self-service. So the customer themselves can log in. You don't have to put in or request to a cloud service provider to go and make this change for you.

2:36You can just log in and do it. Really cool. We have resiliency and reliability. And this is different from on premise in most cases, not all. Because your cloud service provider, they're setting up in this giant data center. In that data center, they generally have feeds from two different power grids, a lot of times. They'll have their own water resource for cooling on site. They'll have their own power substations on site. You see where I'm going with this, right?

3:07They got giant battery banks on site. They spend billions of dollars on these data centers with all this redundancy. Well, you can't do that in most cases for your on-premise setup. We're lucky if we have a decent-sized battery backup or up system to support our infrastructure, and that is one of the great benefits of cloud is all of that added resiliency and redundancy that's built into it. And then we have a reduced cost.

3:40And that's because when you take a look at all that you're paying for on premise and you compare it to the cloud, in most cases, I'm not going to say all cases, in most cases, you will achieve a reduced cost. And this is a reduced total cost of ownership, or TCO. Now, think about this. When you have an on-premise setup, you're paying for those servers, you're paying for all that labor to set them up and then manage them.

4:11If you're using virtualization, you have hypervisors that are running on them that have to be managed and patched as well as the guests running on them, you've got your network you have to manage, you've got for all those things, you have cooling for all those things, and the list grows. It does, I'm telling you, it grows and grows and grows. And when you get down to the nitty gritty of all these things and add them up, guess what? You're probably going to save money in the cloud. And think about this too. For all that hardware that we purchase on premise, we have to buy annual maintenance contracts form if we want to continue to receive support for them and get the updates, which, believe me, I always vote for that because that way you have support for your devices.

4:56You're not out in the cold left alone, and you've got annual licensing costs that come into play as well. And these things add up. So that's where we get our reduced total cost of ownership. So that's infrastructure as a service. So if you're looking to spin up virtual servers in the cloud and run a network, just like you do on premise, then IaaS is for you, and you get all these benefits that come along with it. I hope this has been informative for you. I'd like to thank you for viewing.

0:00[MUSIC PLAYING] Next up in our cloud services is platform as a service or PaaS. Now, this is for all you developers out there. And what this is, is a platform in the cloud that you can use to build out your applications as you see fit. And it's really darn neat. I like to think of this like LEGOs in the cloud for developers, because you've got a platform with all these tools and abilities, and you get to create some pretty cool things.

0:34So let's jump in and further discuss platform as a service. So here is our PaaS or platform as a service. And I said, it's used to develop applications and such. And it's really darn cool. And again, I like to think of this like LEGOs in the cloud for developers, because you can build anything your imagination musters up. And there's lots of cool things they include in these, lots of new things like quantum computing and different things like that, where you can actually tie into these different features and use them in your application.

1:09Now, let's talk about this. So when we're using platform as a service, basically, we're given a bunch of different tools and features that we can use to develop applications which is super awesome. And this could run in a private, public, or hybrid cloud. It gives you lots of flexibility. And it supports multiple programming languages. And, of course, it has lots of scalability like everything else in the cloud. And much of the scalability can be automated so that it's not something we have to manually do.

1:44So you can tie into this as a developer, when you're developing on a platform in the cloud. Now some benefits that we have with platform as a service, other than these up here, are global collaboration, meaning this platform and cloud is available anywhere in the world. So if you have a bunch of different offices around the globe, well, they can all log in and collaborate together on what's being built. We also achieve some cost reduction in comparison to native development, because the idea here is that we can actually use a single vendor to supply all of our needs.

2:27We don't have to go across vendor. So that can allow us to achieve some cost reduction. We also have global access for all the customers using these applications we build because they're available globally. But you might say, well, so is what I build on Premise. I built an application, I opened it up, and anybody can access it from anywhere in the world. Yes, but if you are running this from one single location and you have somebody across the globe trying to access it, well, they're going to see some latency, some slowness, different things like that.

3:03Well, with the cloud you can actually deploy this across multiple data centers around the world to better service your customers. So that is platform as a service and some of its benefits. I hope this has been informative for you. I'd like to thank you for viewing.

0:06All right. The last type of cloud service we're going to talk about is software as a service. This has been around for a long time. We've been using software as a service and didn't even know it was a cloud service per se. And we're going to talk about what it is. And then you'll see why you may have been using this for many years and didn't even realize you were already using cloud services. Software as a service, it's very simple. It's just software that is running in the cloud that you use.

0:39Now, you think, well, my company doesn't have a cloud account, really, and they don't create applications in the cloud. So we don't use software as a service. Ah, but wait, you probably do. Have you ever used web mail? And maybe you did that through a vendor, like you use Office 365 email. Well, guess what? That is software as a service. Do you maybe have some type of HR or accounting application that you log into via a web page?

1:12So I know there's different examples of them out there, like Bamboo HR. These are all different types of software as a service. So when you go and you log in to a website of a company and use an application, that software as a service. So it's really simple. But there are some great benefits, like on-demand access, right? We can access it from anywhere. So we have anywhere access, or global access, and of course, on-demand access because we can log into it whenever we want to.

1:48It also allows us to achieve some reduced costs. Because if we use, let's say, an HR platform, if we want to use that on premise, we'll have to pay for licensing for it. I have to buy a hardware for it, some hardware, like a server, with storage and processing all that stuff, plus licensing for the software, my HR software, licensing for the operating system, support contracts. The list goes on and on and on, plus management fees, blah, blah.

2:19Well, you see, when we talked about our Total Cost of Ownership, or TCO, we see how much it actually cost to run something on site. So this is where we can achieve some reduced costs. We have no deployment costs, right? Because generally it's being set up by the vendor. And we send them some information to populate in it. We're not buying servers. We're not racking servers. We're not doing any of that. We're not spending a lot of money to get up and running. Now, let's talk about something real quick. I want to talk about capital expenditure, or CapEx, versus operational expenditure, or OpEx.

2:55Now, this might be something new to you. These are financial terms. But it plays into, really, cloud services in general because CapEx is when you spend the money up front to purchase all of what you need. So let's say we're going to roll out a new HR platform. Let's just go with that. And we'll say, it's going to cost us $15,000 in hardware. It's going to cost us $5,000 in software.

3:25And then to get this set up and racked and everything done, it's going to cost us an additional $2,000. And we'll say install. There we go. So it's going to cost us $17,000 to get this new HR platform up and running. That would be capital expenditure. We're going to spend $17,000 to get this up and running versus operational expenditure. Basically, at this point, it would be whatever the setup fee is for this new platform.

3:57And it might be $0, or it might be $2,000. I don't know. But the idea here is, then, once we're set up, we're going to pay a monthly fee to use this product, right? And that is an operational expense. It's part of operations. They're paying x dollars a month to use this forever until we're done with it. Whereas a CapEx, we're spending a whole lot of money up front to set this up so that we can use it on premise.

4:29And then we will have annual maintenance contracts and software contracts and licensing contracts that we have to pay every year, every three or five years, whatever it is. But the idea is that CapEx is a large upfront expenditure of capital, meaning money, to get up and running. Whereas in OpEx, this is something we're going to pay for every month. So you'll see the spending is different. And when we go with a software as a service, well, that's an operational expenditure, or an OpEx.

5:02Now that we got that explained, let's go ahead and talk about some SaaS benefits. Well, it's going to be, number one, reduced cost. And this is going to be in most cases because sometimes vendors out there will price themselves just ridiculous, right? We know that. But in most cases, you're going to see reduced cost because we don't have to perform a CapEx, right? We don't have to spin that bunch of money up front to get up and running. And we don't have to pay for labor to get this thing up and running.

5:34We don't have to pay for operating system license, hardware support contracts, all that stuff. We don't have to worry about that because we just pay our software-as-a-service vendor, our operational expense, our monthly fee. How about ease of licensing? Because anybody out there who's dealt with licensing knows what a pain in the rear it can be. We don't have to deal with it because the software-as-a-service vendor takes care of the licensing. We just pay them the fee, and that's handled, so ease of licensing. Less administration-- yes, the application itself we might have to do some in administration, like creating new users and things.

6:11But what about all the underlying hardware that we would have to manage if it was on premise? We'd have to manage the operating system it runs on, manage the server, manage the backups, manage the actual application installed on the server and do the patching for that. There's a lot of administration that just doesn't have to happen anymore, not by us. The software-as-a-service vendor takes care of that for us. And then, of course, global access-- and yes, if you set this up on premise and you set up maybe a remote access VPN, then users could securely access it.

6:49But that's, again, something else you have to administer or manage. Well, that goes away. You can access this software as a service from anywhere. Just log in to the website and access it. So that is pretty darn cool. So those are some benefits of software as a service. I hope this has been informative for you. I'd like to thank you for viewing.

0:06So we just finished talking about the three primary types of cloud services. That was infrastructure as a service, platform as a service, and software as a service. And we talked about the benefits and all the cool things about them. But did you stop to think about, well, if I use this one, like infrastructure as a service, what am I responsible for? Does the cloud service provider do everything, or do I do everything, or is it shared? Well, the answer is it is shared, and that's across all of them.

0:37There's something known as shared responsibility. And that is a super important term to know and understand when it comes to the cloud because that means that cloud service provider is responsible for some things, but not everything. And the customer is responsible for some things, but not everything. So who's responsible for what? How do I know? Well, we're going to talk about that right now. So here is a sample outline of cloud service provider versus customer responsibilities.

1:08Now, when it comes down to the actual responsibilities, these need to be outlined somewhere in a contract. And generally your cloud service provider will have a document that outlines a bunch of this information for you. What we're looking at here is an example. This is not, like, a set-in-stone kind of thing. It could change. So when we talk about physical security-- that's the first one we're looking at. Think about this. This is in the cloud, right? Do you, the customer, have access to the physical infrastructure, the building, the servers in the cloud?

1:43The answer to that is an astounding no. So of course, the vendor is responsible for all of the physical security, no matter if you're using infrastructure as a service, platform as a service, or software as a service. What about the underlying hardware patching? Here we're talking about like hypervisors and the platforms being used and the software that they are providing us with, with software as a service. Well, we don't have access to that as a customer. So of course, the vendor is going to be responsible for all of that.

2:16What about virtualization management, so the hypervisor and the underlying virtual technologies that are being used? Well, as a customer, again, we don't have access to that. So it's going to be the vendor. What about operating system and application patching? Here we start to see the shared responsibility. When it's an infrastructure to service, if I, the customer, am building a Microsoft Windows Server that I'm running in the cloud, I'm responsible for patching that. If I install applications on that server, I'm responsible, the customer, for patching those applications.

2:51But once we move to platform as a service and software as a service, we know that the provider is managing that software that's underlying. So they're the vendor. The cloud service provider is responsible for that. What about firewall and IPS management? That's our Intrusion Prevention System. That's the IPS. And again, this is our edge security protection. Well, the thing is if I'm setting this up in infrastructure as a service, meaning I'm deploying my own firewall, well, guess what? In my IPS, I'm responsible for managing those.

3:24But when it comes to platform and software as a service, where we're building applications and using the cloud provider's applications, they're responsible for the edge security that's being done. What about all the security policies? Well, this is shared across all of them, meaning the cloud provider will have their own policies. But we, as a customer, we should have our policies too. That's very important. Policies are super important when it comes to security.

3:55We need to define-- let's say infrastructure as a service. We're talking about IaaS. We need to define how we're going to use the IaaS. What policies are around it? Do we have policies around who can create and the creation procedures for cloud services? We should. What about platform as a service and our software as a service? How are we going to use those? Are we going to use secure coding techniques? All these things come out in policies. And then lastly, data encryption. Now in IaaS, I'm building servers.

4:28If I want to encrypt that data, hey, that's on me, the customer. In platform as a service, I'm out there, and I'm building this app that all our people are going to use. Well, I built the app as a customer. If I want my data encrypted in the app, well, that's on the customer. But if I'm using, let's say, some type of HR or accounting application or CRM application in the cloud, well, that's on the vendor. I can't encrypt that as a customer, right?

4:59I don't have access to that kind of thing. All I can do is use the application that I'm paying for. So that falls back to the vendor. And again, these are just some examples of different features within the cloud, within IT in general and our services, in how these are shared responsibilities. The cloud vendor's responsible for some. Customer's responsible for others. And again, this is not like a de-facto standard list that we see here. This is just an example.

5:31Because when you go talk to your cloud provider-- you're shopping around trying to find one. You need to discuss who's responsible for what, and it needs to be outlined in your contract. I hope this has been informative for you, and I'd like to thank you for viewing.

0:06Technology changes every day. That's just a fact of life. We know that. So there's new things like blockchain and quantum computing and Internet of Things, IoT. And there's lots of other things too. But when these things come out, how will they affect cloud computing? Now, we have some of these, and they're actually already being used there. But how are they being used? Well, let's jump in and take a look. We're starting off with blockchain. And that's one of those newer technologies.

0:37It's been around for a while, but it's still kind of new to a lot of us. And it's all about the decentralization of data. And that's what blockchain is all about. Now, a lot of people think blockchain is all about cryptocurrency. And really, cryptocurrency uses blockchain to make it so reliable and robust. But you can use blockchain for lots of different things, including the cloud. Now, when cloud first came about, the idea was that we could take our on-premise assets, and we could take those and move them to the cloud.

1:14And the idea was in the cloud we have lots of resiliency and redundancy. We don't have to worry about power and cooling. A lot of that was offloaded from our local admins and our local costs. So our assets resided somewhere else at a remote data center. Now, wouldn't it be cool, though, that if we could instead of putting it in one data center, we could have our assets copied across different data centers all over the globe. And that would provide for lots of redundancy. Well, that's what blockchain's all about, decentralization of data.

1:46And what it does is it takes the data and it puts it in these different locations. And not only that, built into blockchain is a way to verify and validate the integrity of the data. That is super important. That's what blockchain really is all about. It's decentralizing data and validating and ensuring its integrity, that the data hasn't changed. So if we could use blockchain in the cloud, our data wouldn't be stuck in one data center or stuck in maybe two data centers because we replicate between them.

2:19It would be in multiple data centers all over the world, individual copies of our data. And we wouldn't have to worry about data corruption or tampering anymore because of the integrity. We would immediately know if a piece of our data had been tampered with or was corrupted, and it would no longer be valid. So we wouldn't have to worry about corruption of data. It would be a thing of the past because blockchain would just simply get rid of that data over there and then copy good data over and replace it.

2:52And that way it's kind of a self-healing environment at that point. So that's how blockchain could impact the cloud. Next up AI-- that's Artificial Intelligence-- and ML, Machine Learning. And the idea here is we're using algorithms to teach computers and programs to identify abnormalities and to analyze data and look and see what's going on. And really, a lot of times we like to integrate AI and ML into security products because they're very good at identifying abnormalities.

3:29And that's what we look for in security. What's abnormal? Does this user normally log in to this server at this time of day from this location? And this is how we can really beef up our security and take it to the next level. Well, how could AI and ML be used in the cloud? Well, a lot of times they're used in security services in the cloud. When the cloud vendor comes out with a new security service to help us identify abnormalities and manage our security, it will include AI and ML in it. But not only that, they will offer ML and AI services for us to use.

4:04So when you're looking at platform as a service and you're looking to build an application, a lot of times you can use services that include AI and ML as part of the platform as a service. So you can use AI and ML in your applications you're developing, which is pretty darn cool because these oftentimes come with a large price tag. So if I wanted to implement this into my on-premise something or other, I would have to spend a lot of money to get that up and running in my environment. But I don't have to in the cloud.

4:34The cloud service provider has already done that and can provide that service to me, which will definitely save me a lot of money. And it makes accessing an entry into the AI and ML world a lot more accessible. Next up is containers. Now, containers are basically-- they're virtual machines but, I'm going to say, without an operating system. So they're a virtual machine without an operating system. How does that work? How could that even work? Well, here's how it works. Really, what we have is we have some type of content OS or container platform.

5:09And these are things like Kubernetes and Docker over here. And the idea is that we would have this container OS or container platform here and within it we would run our tiny VMs. And all these VMs-- which are really containers. These VMs, or containers, contain an application. And they can contain the dependencies that this application needs to run, and that's all that's in there. So we don't have an operating system in there.

5:40We don't have a bunch of bloatware that comes with an operating system and other things. We just have exactly what we need-- very lean when it comes to running a container. So here we could spin up containers, as many as we need to very quickly, because containers, they might only need 50 megabytes of memory in order to run. And maybe they need 80 megabytes of actual space, like hard drive space. So you see, it's very tiny, and that's why they're so popular.

6:10We can spin them up within seconds because it may only take five to eight seconds for one of these containers to start up and be usable. That's a lot faster than a full-blown operating system. We know it takes minutes for those to get up and running. So how does this tie into the cloud? Well, here's how. Within the cloud, the cloud providers have taken these container OSes and platforms and they've put them in the cloud so that you can use them. You can spin up containers.

6:41But why would we want to? Well, here's why. Remember, this is a pay as you go. It's a metered service. You're only paying for what you use. Well, if I'm only paying for this little bit of resources versus a full-blown virtual machine server, there's a big difference there. And when I'm dealing with applications in the cloud-- maybe I have a big database back in here, and I have a front-end web app that interacts with my back-end database. And this is a very static web front end.

7:12So it's just a static web page that people use interact with. And during certain times of the day, I need to really spin up a whole lot of these simple web front ends to handle the load. Well, isn't it a lot faster to spin up a bunch of containers, as opposed to a bunch of full-blown servers? The answer to that, yes, absolutely. So maybe I normally run five of these NginX. We'll say they're NginX containers. And that's normal.

7:42But during my peak loads, I need to run 50 of them to meet my client and customer demands. Well, if I spin up 50 containers, as opposed to 50 virtual machines, hey, it's going to spin up a lot faster. And I'm going to use much less resources. So I'm paying for less. So I get to reduce what I'm paying for, and I get to respond faster. Hey, that's a double win in my books. So this is how containers can affect the cloud environment.

8:14Next up, quantum computing. Now, quantum computing, if you're not familiar with it, it uses quantum physics as opposed to transistors or micro transistors within a general processor. So within a general computer processor that we're used to, a CPU we got over here, well, they're full of micro transistors. And a micro transistor is basically a switch. And a switch is on or off. So it's 1 and 0. And this is how we get our binary ones and zeros.

8:46Micro transistors act as a switch, and they're either on or off. So here we are definitely limited to how much data we can store and process. Well, with quantum computing, it actually uses quantum physics instead of our micro transistors, which means it can store not just ones and zeros, but it can actually store multiple values. So if we are able to get these up and running like science says they should be working, then we will have amazing processing power.

9:23And quantum computers have already been created, but they're not yet quite to the mind-boggling compute power level. So how does this tie in to the cloud? Well, some cloud providers, they've already purchased and have quantum computing-- put a Q there-- in their environments. Well, why does that matter? Well, here's why it matters. They can offer you access to these as a service. Could you imagine how much these are costing right now? I have no idea. But I would say it's a whole lot.

9:54Anytime a new technology comes out, it is extremely expensive. So that means most organizations cannot afford to use it. But what if you just wanted to do testing with it, or you wanted to run your application through it for half an hour, a day, whatever it might be? Well, then you can go to your cloud service provider. You can sign up for their quantum computing service and only use as much as you want to because, remember, you're only paying for what you use. So this is a way for cloud service providers to allow an entry level, an easy way to gain access to, and an affordable way to gain access to quantum computing.

10:29And lastly, IoT, Internet of Things. Now, the internet of things are all those smart devices out there. They could be a smart phone, your smart light bulbs, smart houses, Wi-Fi devices, all kinds of things, our smart thermostats. All of those things are referred to as IoT devices. OK. Well, that's nice. But how does that relate to-- yeah, you guessed it. We're tying it back to the cloud. How does it relate to the Cloud well, we need something to manage all of these devices.

11:03And guess what? Cloud providers, those CSPs out there, they've already done this. They've provided IoT as a service. So you can actually go out to them. I know AWS has it. And you can sign up, and you can start using their services. So what you can do is you can create applications that will run on these IoT devices. And you can manage them and collect data and do what you need to. So instead of trying to create an IoT infrastructure from scratch and figure all that out, there's no need to.

11:33You can go to your cloud provider and use IoT as a service. That's a new type of thing so that you can create and deploy and manage your own IoT environment, which is pretty darn neat. And really what it comes down to is all these new technologies and things, it is a way to access them. The cloud provides us a way to access them, and not just the cloud itself per se, but those cloud service providers. The providers are going out there. These CSPs, the larger ones, they have a lot of resources, and they can go out and they can gain access to these new technologies.

12:09And they can deploy them as a service so that we as consumers can gain access and use these new technologies to our benefits without going out and creating the huge environment so we can support them. We can just tap into the resources that the providers are providing us with. So this is really darn neat. And it's a great way to get started in some of these new technologies. I hope this has been informative for you, and I'd like to thank you for viewing.