3 hours 51 minutes
Welcome back to Microsoft Azure Fundamentals. This is Module six Azure Compute Services.
In this module, we will learn the compute concepts in Azure.
Then we'll get into the details of azure virtual machines as your container services, as your APP services and as your server less computer.
While discussing those will try to outline the best way to use those services in your solutions,
we will look at where those services are most appropriate to use and where not as well as the cost for using them.
Let's get started.
Compute services in the cloud allow you to perform calculations, run custom business logic or applications.
Let's look at the compute concepts that are at the core for azure compute offerings.
Azure offers four different ways to perform. Compute
virtual machines provide software emulation of a physical computer.
They have a virtual processor, memory, hard drive and networking interfaces and require operating systems installed on them.
You can connect to the virtual machines using a remote connection software like Microsoft Remote Desktop client or Lennox ssh client and use them as if you were sitting in front of them.
Virtual machines offer the most control, and you can install almost any application on them using legacy off the shelf software
containers are the next compute option in Azure,
similar to virtual machines, containers run on top of a host operating system. They do not require their own operating system installed inside the container.
Instead, they bundle all the libraries needed by the application and use the kernel of the host OS to run the container.
If you have several containers running on that server with Lennox, all those containers share the same Lennox colonel.
What that means is that you have less flexibility mixing and matching different operating systems on the same host.
If you need to run containers that require Lennox Colonel, you need to run this on a Lennox host.
If you need to run containers that require windows, you need to run those on a windows host.
Azure APP Service is the platform As a service compute offering in azure,
it is designed to host highly scalable enterprise grade Web applications.
You can create an instance of the service and choose a runtime from your preferred choice like dot net PHP node dot Js or Jabba and deploy your own custom code.
You don't need to maintain the underlying infrastructure but have some control of the runtime configuration
that allows you to meet different requirements like performance capability, security and compliance with lower maintenance costs.
And last but not least, server list offers a cloud execution environment for your code. With complete obstruction of the underlying infrastructure,
you can deploy your own custom code and run it based on various triggers. Like schedule http or event triggers
Asher takes care of all the infrastructure management. Of course, this means that you have no control of the environment configuration
now, Depending on the need to grow application, you may choose more than one compute option.
For example, you may have your online shopping website deployed on azure APP service and submit the processing of each order to a server. This app.
In order to properly design your application, you need to be aware of the capabilities and the restrictions of each option.
We will look into each one in detail in the next few videos