Here's another image of Docker workflow.
Again,
I provide all the attribution in the lower left corner
here. I only take credit for my own art.
What I want you to see here working from left to right is the developer will
use Dockerfile. Now, it goes beyond that. You can actually create
multi‑container setups using what's called Docker Compose, and that uses a
YAML syntax, etc. Check the Pluralsight library, because we have plenty of
Docker training if you want to go deeper.
But for a single container,
like let's say the developer wants to create an IIS web server Docker
container. They can do that absolutely, with their Dockerfile and their
Docker Client tools they'll create an image. And as I said,
the developer will want to post that image to a registry.
Now,
Docker Hub is Docker's own public repo. You can buy
access to create private repos.
What we need to know for AZ‑800 is Azure Container Registry, or ACR.
This is the Microsoft Azure‑hosted container registry.
And as you'll see in the demo, Microsoft made ACR so that your
developers and infrastructure people can continue to use their Docker
tools. So you use docker push, docker pull,
you don't have to use PowerShell or the Azure CLI, although you could use the
Azure CLI if you want to. Microsoft wanted to empower everybody, their customers
that is, to be able to use their existing tooling to interact with Azure
Container Registry. Azure Container Instance is an Azure‑hosted Docker daemon.
It presents an alternative to having the Docker Server running on a VM, let's
say, or in your local environment. You can just spawn these containers, and even
more to the point,
you can spawn containers from images that are in your Azure
Container Registry and host it all within Azure. Now Azure
Container Instance is fine, it works great,
but it's not necessarily enterprise scale.
For high availability and enterprise scale,
you've got Azure Kubernetes Service, or AKS. This is a
Microsoft Azure‑hosted Kubernetes cluster.
There is another option called Azure Service Fabric.
It's very similar to Azure Kubernetes Service,
but it's more proprietary to Microsoft.
Microsoft appears to be de‑emphasizing Service Fabric
and pointing customers to Kubernetes.
And, again,
because Kubernetes is available on‑prem and in other clouds, I would recommend that you standardize on AKS rather than Service Fabric.