[MUSIC] Hi Josh Hiliker and as we start the cloud services module, I'm going to talk a little bit about cloud services overview 101. As we explore the cloud services discussion. What are we talking about in this section is around global scaling concepts, core principles and the different types of cloud services. So why are cloud services growing? Well, it's that access to innovation, faster innovation. It's about cost effectiveness and no capex costs upfront. It's about that scale capability. So being beyond your walls, beyond your company, it is about being able to stay up to beat with the hardware. So you're not using obsolete older hardware, you're using new the fresh, what's coming out and be able to try things at a very different beat rate. Here's a practical guide for popular cloud offerings, infrastructure service, platform service and software as a service. And you'll see the types like whether it be from email on the top or database and platform side and then from a full instance down at the bomb infrastructure as a service. These are the examples of some of the product names. It's good to spend a moment, look over the product name so you get an idea of what's there. Because you'll hear it in context, you'll hear it when customers are talking about it, you'll see it when you read cloud computing journals and cloud computing articles online. So how does selling a service work? Let's pick infrastructure as a service and specifically a dedicated host. There are three types here. There is on-demand, reserved and spot. On-demand is I'm going to use it right now. Reserve is I'm want to reserve for a period of time. Like I'm want to reserve it for the next three years or I want to reserve it next quarter and then there's spot, I want to use it when it's available at the lowest cost. I'm not trying to use give all models here, I just want to give an idea of what's out there when they talk about, how does the service get sold? What does a consumer look like when you go online to actually use this? What's presented as the options? So with core cloud principles will kick us off with distributed data store. What that means is that you can have data on multiple nodes and being able to scale it, replicate it and move it around. That means across different networks, across different nodes, across different regions. It is about being able to keep your data in different places. So you have that redundancy availability, that you need with your data. This means for in the cloud space that I'll be able to access my data when I need to be able to make sure that I have redundancy in case there's a failure. Super important principle. Let's get you on with core cloud principles and this is concurrent computing. This is not the serial processing and waiting for actions to complete out. This is about software. Optimize that looks to what's available and computing in parallel, so that concurrent nature. This great cloud does it. It gives your ability to execute more in a faster time rate versus being I'll do it serially on one machine. I'm now going to shift over to scaling concepts. Scaling concepts are important because that availability redundancy, but you'll know where your data is at and be able to access it. So and not just data, but applications. So for example, if you have users in one geography and that's where you want the lowest latency, you may want to move your data, you want to move your application close to it. So knowing how you scale in the cloud space is very important. So here's a couple, regions and zones. So a region is a geographical region, okay, so like the United States, a zone would be East coast, West coast. So you've got a zone on the East, maybe a couple of data centers in the West, maybe you got half a dozen data centers, those are zones. It's important we're doing cloud computing and for the cloud service provider, when you work with them to know where do I need to access it? How does it, who's going to be computing on it and then be able to put it in the right region or zone that's appropriate. Now let's continue on and talk about resource groups. When we talk about scaling concepts we talk about resource groups and resource managers. A resource group is being able to take everything and put it into a group and then manage it as a single instance.. Which is helpful because you can take a project, take an application, put all the all the different components of the application into a resource group and manage it. Resource managers, these are the tools and methods to help you manage your projects in the cloud. It is part of that scaling work. Now let's talk a little bit about the edge, okay. Two aspects there's edge cashing and there's edge servers. Edge cashing is getting that information out to the edge where it needs to be. So for example, if there's a really cool video and everybody's downloading it. Being able to cash that content like to the edge is important. So you have better replay, latency is down and you can put it local to them, so there's not a bunch of calls back to the source. Now for a CDN edge server, so a content distribution network edge server, this is putting that server close to the edge and being able to get the content there. So it's faster whether it's a movie, a video, a picture that everybody has been looking at and using being able to put it out at that location. So you're distributing your network out, you're putting these CDN edge servers out there on the edge and then be able to use them to do you're cashing and for file access. And I guess until the file expires and that exploration rate could be on a 24 or 48 or whatever the amount of time required for that specific object. But that way you can call back to remote check in, hey, is there a new version of this and be able to push the new version out to all the edge servers using that cashing. Now let's finish out scaling concepts with high availability of services, high availability matters, in the cloud, you're able to say where do you want your data? You want multiple versions of it? You want it to be able to access it? So the same data is being replicated between servers. So if there's any kind of issue with one region or zone or dc, you're able to then access the other location without even missing a beat. And that's important for that if you've got a critical application where latency matters, you've got a critical order inside you have something that's happening where it's critical to have your data. Or you're just store your data in the cloud and you want high availability for it to be able to replicate and be able to access it when you need to. And a cloud service provider, cloud security has two areas of concern. One is what the customer owns. Two is what the service provider owns. The service provider owns that physical securit. So making sure that no one can access your hardware, no one can access your capability and make sure no one can physically get in. They're going to make sure there's physical perimeter and physical security. From a customer standpoint, it's about making sure your applications are hardened and make sure that you've protected yourself. You set up your VPC in a way that no one can get into it. You've got access at the right levels between application layer and database layer between web head and application. You own that as the customer of it so hard during it, making sure it's good, all the service provider make sure it's been bios updates, patches has happened and it's got physical security of that hardware. So two different security concerns. It's important to know because you have different expectations on who does what and when things need to happen during creation, during startup, during changes. Let's talk about two of the roles that are in the cloud service area. SRE site reliability engineering and DevOps. Site reliability engineering looks at using software to get the reliability you need, DevOps is a software engineering bind set. It's the philosophy, it's the process, it's kind of how does that pipeline work? So it's difference between how and what. The SRE role brings both DevOps and they're rolled together into one. Why does this matter? The cloud it's about availability, it is about reliability, it is about scalability. So the SRE role is very important because they're thinking about that. And so when you're talking to a customer, it's important to know what's the role of the person you're talking to and knowing these concepts. So you're thinking all rady about, okay, reliability, I'm thinking about availability, I'm thinking about how you're breaking it up. So as you have a conversation with a customer, you kind of know where they're coming from. How is your application setup, how is your back end setup? And you'll know really quick on who you're talking to. If you're talking to the DevOps, you're going to know real quick what's going on there. If you're talking to the SRE,they're looking at a different picture. That's why these two rules are important to know and that's why I'm calling them out today in this section. As we continue the fundamentals for cloud services, these concepts and principles are important. It's about getting that faster time to what's next, the faster time to market.It is about getting the availability, the redundancy, the ability to get your content the right place. It is about knowing the roles of the folks that are in the cloud service, like the SREs and the DevOps on who you're talking to and what kind of language you're going to pick up in those discussions. Thank you for joining me on cloud services overbiew 101.
