Join David Elfassy for an in-depth discussion in this video Fundamentals of cloud computing, part of Understanding Microsoft Azure Core Functionalities.
- If we're gonna get familiar with Azure computing, we first need to get familiar with Cloud computing as a whole. Understanding some of the terminology of Cloud computing, and some of the standards that are implemented through Azure. So when we talk about Understanding the Clouds, we're talking about Understanding the terminology and the services that are deployed in private Cloud infrastructures, as well as public Cloud infrastructures. And we're gonna determine that in a few minutes. We actually have three different types of Clouds: Public, Private, and Hybrid.
Hybrid is really a combination of Public and Private Cloud offerings. So let's take a look at the differences between these various Clouds. But before we do that, let's talk about On-Premises. So when we talk about an On-Premises infrastructure, we're talking about an infrastructure that's deployed within your company. You manage the hardware, the services, the firewalls, pretty much everything in your organization is being managed by internal administrators. And you are responsible for all of those services, as they function and provide functionalities for the users, in your user population.
Your users then consume those services, and as they consume them, you need to update and upgrade and manage the hardware that the services live on. On-Premises infrastructures have been around for many, many years, and many administrators today are very familiar with managing enterprise services On-Premises. As we talk about moving to the Cloud, we look at how these type of offerings get transferred into a Cloud-like functionalities or Experience. For example, we have the Private Cloud, and the Private Cloud is really An On-Premises Cloud Experience, whereas a user, and that user could be an administrator, has a Portal-based environment from which they can manage the infrastructure, provision servers, deploy applications, manage websites, all of those things can be configured and managed from a Portal-based environment.
Almost hiding the infrastructure that is in the background, and exposing only those Portals for managing to administrators. A Private Cloud infrastructure depends on software that manages that Private Cloud, and that exposes all the functionalities and the Portal. A good example of that Private Cloud software is System Center 2012 by Microsoft, which provides a Private Cloud Infrastructure. It is typically Stored in a private data center, so you are still responsible for the hardware.
You're still responsible for the software and all the network services. The level of responsibility that an internal organization has for a Private Cloud is really no different than an on-premises Infrastructure. The primary difference is the Experience of managing the Infrastructure. And then we talk about a Public Cloud. Now you know about the Google Public Cloud, Amazon Web Services, and of course Microsoft Azure. You've heard of Microsoft Azure and you understand that Microsoft Azure provides this Public Cloud functionality, and as a Vendor, is Responsible for "Most" Tasks that are performed within their Azure infrastructure.
The Public Cloud Uses a "leasing"-based model, which basically is a Pay as you go, or Pay as you use type of infrastructure. So, as you consume resources, whether those be applications, or workloads, services, or infrastructure as a whole, you Pay based on your usage. That usage may be the amount of data that is stored in the Cloud infrastructure, as well as the services offered by virtual machines, for example. A great advantage of a Public Cloud infrastructure, is that you have this entire infrastructure that's already there, and if you need to deploy a New application, or you need to deploy a New server, you can do that very quickly, and at a very low cost, because you don't need to purchase new hardware to support that additional infrastructure.
Sometimes, simply purchasing hardware for an organization can take weeks or months, especially in large organizations. If you have a Public Cloud infrastructure, it can be just as quickly as a couple of minutes to provision a virtual machine, that will then store or host all the services that you wanna make available to your users. When we're looking at a major operational difference of a Public Cloud, is that we're really Reducing the capital expenditures of a company. You no longer need to spend as much money on your servers and your networking hardware.
You can Reduce those. However, you will have a major increase in operational expenses, the expenses that are recurrent on a monthly basis, to support the usage of your Public Cloud. Whether you decide to go with an Azure Public Cloud, or an Amazon Web Services to host your virtual machines, the model is really quite similar. It's a monthly "leasing" based on usage. In the next video, we'll talk about the various subscriptions, and the cost models that are associated with the Azure Microsoft solution.
Now there's also the Hybrid Cloud. Now the Hybrid Cloud is a true Mix of Public and Private solution. Whereas you can have your own internal, Private data center, and then you may choose to store some workloads, some services, some applications, over into the Public Cloud. You may store those in the Public Cloud, because that may be the right environment for that. It may be less costly to deploy that data, or store that data into the Cloud, rather than to purchase new storage hardware to move that data over.
So you truly get to choose the best environment for either your data, your services, or your application, based on your security needs, or your cost needs, or other organization needs that you may be running into within your company. Now there are many customers, or many organizations, that are reluctant on moving to the Cloud for various reasons. Some of those are political reasons, where they want to limit the replication of the data to other countries. Now there's actually solutions in Azure where we can segregate the data, and specify where it gets replicated, and where it doesn't.
But that perception still exists, where people may not want to do a full migration to a Public offering, and in order to limit that, but still get the benefits the Public Cloud, the Hybrid Cloud, or the Hybrid solution, gives you the ability to only selectively put resources into the Cloud, that for which they are appropriate. Now keep in mind that if you have a Hybrid Cloud solution, it's definitely gonna be more complex to manage, because you have to manage both environments, as well as the coexistence, or the communication between both environments.
- Understanding Azure subscriptions
- Managing Azure with portals and PowerShell
- Configuring Azure web apps
- Deploying virtual machines
- Configuring virtual machines for high availability
- Managing Azure Active Directory
- Creating Azure virtual networks
- Implementing a VPN
- Performing Azure backups