Translated from 日本語 • View original Hello, this is Akakawa, an infrastructure engineer.
We continue to participate in Build 2018.
There was a Key Note on the first day and today, but it included updates not only for Azure, but also for HoloLens, Microsoft products, Visual Studio, etc., and I often didn't understand much about Office products. By the way, the most exciting thing today was the LF line break code support of notepad.
Key Note: After the session, a work shop, and an exhibition hall are available.
Today, I would like to compare the two clouds with Container services.
Container
Even when I looked at the Key Note and the session list, the characters in Container, especially kubernetes, stood out. If you check the Azure Container service here,
- Azure Kubernetes Service (AKS)
- Azure Container Instances(ACI)
- Azure Container Registry(ACR)
- Azure Service Fabric
- Azure App Service
- Azure Batch
It seems that there is.
On the other hand, if you check AWS from here,
- AWS Fargate
- Amazon Elastic Container Service(ECS)
- Amazon Elastic Container Service for Kubernetes(EKS)
- Amazon Elastic Container Registry(ECR)
was raised.
Although not included in the above URL, Elastic Beanstalk also supports Docker containers, and AWS Batch also builds clusters on ECS, so they are part of the container service, and both are comparable to each other.
Azure Kubernetes Service
Originally, it was called Azure Container Service and supported three orchestrators: kubernetes, Docker Swarm, and DC/OS. After that, it was renamed Azure Container Service (AKS) in Kubernetes, and recently changed to the current Azure Kubernetes Service.
It seems to specify the number of nodes, so it is not a simple comparison, but is ECS/EKS the opposite?
Azure Container Instances
Containers can be launched as nodes in a clusterless manner. It seems that if AKS runs out of cluster capacity, ACI pods can be scaled out quickly.
"Flexible Bursting ACI with AKS provides isolated, high-speed compute that can handle exponential increases in traffic. You don't need to manage the server. For example, in Azure Container Service (AKS), you can use a virtual kubelet to provision pods within ACI that start in minutes. As such, AKS runs at just enough capacity for an average workload. If your AKS cluster runs out of capacity, you can scale out additional pods with ACI without adding additional servers that need to be managed. "
Azure Container Registry
A private registry service that stores container deployment images.
Azure Service Fabric
In order to realize Micro Service, Container alone is a service that automatically expands distributed systems using Micro Service Architecture and Microsoft's proprietary orchestration technology to cover the scale of the application itself. Since it is a service that was announced a few years ago, I guess it means that I have recently switched to kubernetes.
For more information, please refer to the Azure Service Fabric overview here.
Azure App Service
If you check the service description,
- Web Apps
- Web App for Containers
- Mobile Apps
- API Apps
Four were listed as details of the service. It's a "fully managed platform," so if you only need to focus on your applications, Elastic Beanstalk seems to be a close service.
Build 2018 is also tomorrow and the last day. I would like to touch as many Azure services as possible and return home.
2018/05/09 Some content has been changed.