Join Mike Benkovich for an in-depth discussion in this video Getting started with Azure, part of Azure Enterprise Development: 1 Governance and Infrastructure Deployments.
- [Instructor] When I look at bringing Azure into the enterprise, there's a number of key benefits that I really want to be able to realize. Things like being able to provision services and compute quickly and easily, being able to have my system run whatever technology stack I happen to use. I want to be able to connect it up to my existing on-premises applications and I want to have it span across different things, but I also want to be able to secure it and lock it down. I want to be able to respond to demand and scale up as needed, and then, when the demand goes away, I want to make sure that it scales down.
I want it to be reliable. I need to make sure that it's there, that it fits my customers' needs when I need them, and I want it to be visible so I can see exactly what's going on. The types of cloud services that we run when we have our systems running on-premises is that we have to manage the entire stack, everything from the hardware all the way up through the applications, worrying about patches, worrying about backup. If I have a need for more compute capacity, I have to actually go out and buy new hardware.
And there's a time to market to be able to acquire and bring those machines in. When I look at the cloud, I have the opportunity to go out and provision what I need when I need it, and I can do that fairly quickly. Even when I do, there are still a couple of phrases and terms that you should know. Infrastructure as a Service, for instance, talks about a type of cloud service where you're managing the applications, the data, you're basically running virtual machines on someone else's hardware. I still have to worry about the patching and I have to worry about the networking and the middleware, but the cloud will allow us to go out and virtualize running those machines and servers.
When we look at Platform as a Service, we're really focusing just on our applications and our data, and we're taking advantage of the infrastructure that is provide inside of the cloud to take care of things like making sure that the instances are updated and then patched the way that they should be. Software as a Service is another term you might have heard. SaaS, it is where I've got a service that I'm going out and I'm provisioning, I'm running things like email would be an example of a Software as a Service where don't really care how it's hosted or where it's running, I just want to be able to go out and use it.
There are different types of cloud deployments as well, and a public cloud is where companies like Microsoft or Amazon or Google have data centers, spread around the world, and you're sharing those data centers with other customers, but you're running your systems on other people's hardware. Private cloud is where I've implemented a lot of virtualization. That virtualization makes it easier for me to be able to go out and allocate compute and storage and network to particular applications, and I can shift it around, but I'm really running it all inside of my own data center, so a private cloud actually is really based a lot on virtualization.
So, what the hybrid is is it's literally taking my own data centers and I'm just extending it into the public cloud and taking advantage of the burst in elastic capabilities of what it can really go out and do. So, the path to modernizing is we're really going from on-premises where we've got our own hardware dedicated for our application requirements. We might have a whole set of different things that we're trying to manage. Virtualization is where we include things to be able to go out and create virtual machines running on hardware, but I can split up the machines across as I need to to fit what my applications are.
Cloud virtualized is where we are picking up those VMs and running them, sometimes in the cloud, sometimes on-premise, but we're leveraging that same technology to move things back and forth. Containers is another technology that's just come out. I mean, it's like Docker, you've got all of these different kinds of mechanisms for being able to not have to worry about the entire operating system, but more about how I've got the right set of libraries and all the other pieces that make that application work, and I'm literally going back and forth and trying to get a container which has all the dependencies.
So, I might have a particular version of .NET, I might have a particular set of encoding DLLs and other binaries that have to be there for that application to work, but I deploy it in a way that packages it together that runs inside of a container service, such as Docker or Kubernetes, and I can use that, then, to densely deploy out instances of those containers as I need to. So, containerization is a nice way to modernize my applications. Platform as a Service is where I architect from the ground up and I might have to rework, I might have to refactor my applications to really take advantage of it, but the idea is that that really will get us a lot further and closer to where we want to be.
What serverless is is it's using existing technologies such as functions and Lambda in AWS to go out and do burst, just-in-time compute, and just-in-time storage, and I'm looking at data and the data's in motion. A lot of IoT processes are using all of those kind of data flows where I really want to pull that value out while the application is actually moving. There's a lot of different uses for cloud computing, things that we talk about, like putting up new applications, putting out new websites, doing backup, storage, working with blogging.
You can ingest data, deliver software on demand, but there's a lot of different uses and to meet these demands, Azure has a lot of different service offerings that you can choose from. And depending on where you're at with your application architecture and the model you're trying to go for, you can go out and choose from each of these different services and put them into an architecture that you go out and design. So, everything from compute and networking and storage, all the way up to data in motion, enterprise integration, security and identity.
There's all these different services, but to use them, we need a subscription, so let's take a look at creating a subscription.
Learn best practices for resource governance with resource groups, policies, tags, and role-based access control. Discover how to configure the infrastructure you need by provisioning virtual machines and creating virtual networks that connect your existing data centers to the cloud. Review the Azure disaster recovery features, and then learn how to use templates and automation to provision and deploy services more efficiently and consistently.
By the end of this overview, you will better understand the potential Azure has and be able to get the most value from the cloud. Watch part two of the series to learn how to modernize your apps with application services and the Azure PaaS offerings.
- Setting up an Azure subscription
- Implementing tags and policies
- Provisioning virtual machines
- Using Azure templates
- Operationalizing a virtual machine
- Using SQL Azure for data storage