Start designing a hybrid cloud in Azure and come up with a working business model for your hosting solution. This course walks you through the design process, cost estimation, and concludes with a sample business case.
If you're an IT architect or admin, you can learn the skills you will need to design a hybrid cloud in Azure and put a business model together. This course will cover what you need to know so that you can put your design and business case together. First, you will take a set of requirements and create a high level design. Next, this design will be used to estimate the costs of hosting the solution in Azure. Finally, you will bring everything together and figure out how you would approach a business case. By the end of the course, you will have a much better idea of how to design and host your hybrid cloud.
Course Overview Hello, and welcome to Pluralsight. My name is Gavin, and this is the Designing a Hybrid Cloud in Azure course. This course is designed to get you up and running quickly without any prior knowledge of Azure. What we're going to do is take a typical set of technical and business requirements and we're going to turn them into a bill of materials. A bill of materials is how we're going to understand our costs for our hybrid cloud. Throughout the course, we'll spend time going through the high level technology that makes up this this build materials. After all, it's important to understand what we're pricing. Once we've laid out our high level design, we're going to start to put together those cost estimates, so we'll spend some time trying to understand the common pitfalls before finally putting the model together. We're going to conclude with some cost saving tips and examples taken from the real world of Azure design. And then finally, we'll close out with what you could include or should include in your business case and your overall project.
Before Starting the Design Hi. This is Gavin, and this is the Before Starting the Design section. With cloud projects, there's a tendency to jump straight into the technology. The cloud has virtual machines. Hey we need to virtual machines. Let's just go. Let's just do it. You see the problem with the approach is that you're going to miss a lot of important information. Cloud projects are more than just memory and CPU specifications. So in this module, we're going to discuss some of the other important things that you need to consider before starting your design. For example, do you know where the users of the system are? Do you know how many there are? Do you know where they are located? Are they all on corporate networks? Are they remote users? This type of information is really critical because it'll help you design the system. It will have a big impact on the network design. It'll have a big impact in the delivery of the application. You also need to know a lot about the supplier and vendor of the software that you're going to put up in the cloud. It's important to understand their licensing models. It's important to understand their cost models. And often overlooked, it's important to understand their support models. Part of going to the cloud is understanding the criticality of the application. This will allow you to determine the high availability requirements and understand the disaster recovery requirements. It's a balance. It's a balance between cost and it's a balance between complexity. I mentioned licensing briefly earlier. Licensing kills cloud projects if you get it wrong. It's important to understand your vendor's licensing models. The Microsoft licensing models are also a little bit complicated, but we'll go through those later on in the course. The last thing to watch out for is security and compliance. Depending on the industry you're in, you'll really need to understand what security and compliance certification Microsoft Azure has. Even if that if information is not asked for, it is always important to include it, and we'll talk about that more later on in the course. So what are the goals for the module? Well I'm going to talk about the sort of questions that you should ask before starting your high level design.