You are designing a container solution in Azure that will include two containers. One container will host a web API that will be available to the public. The other container will perform health monitoring of the web API and will remain private. The two containers will be deployed together as a group.
You need to recommend a compute service for the containers. The solution must minimize costs and maintenance overhead.
What should you include in the recommendation?
Click on the arrows to vote for the correct answer
A. B. C. D.D
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-container-groupsBased on the requirements of the scenario, you need to recommend a compute service for two containers. One container will host a web API, which will be available to the public, while the other container will perform health monitoring of the web API and will remain private. The two containers will be deployed together as a group, and the solution must minimize costs and maintenance overhead. Here is a detailed explanation of each of the options:
A. Azure Service Fabric: Azure Service Fabric is a distributed systems platform that simplifies building and deploying microservices-based applications. It provides built-in application lifecycle management, making it easy to deploy, upgrade, and manage your applications. Service Fabric can run containers, but it is not optimized for that use case. It is better suited for hosting stateful services that require a high degree of scalability and reliability. Service Fabric has a steep learning curve, and it may not be the best option for this scenario, where you need to minimize costs and maintenance overhead.
B. Azure Container Service: Azure Container Service (ACS) is a deprecated service that provided a way to deploy and manage containers using popular open-source tools like Docker Swarm and Kubernetes. ACS is no longer recommended for new deployments, and existing deployments should be migrated to Azure Kubernetes Service (AKS).
C. Azure Kubernetes Service (AKS): Azure Kubernetes Service (AKS) is a managed Kubernetes service that simplifies the deployment, management, and scaling of containerized applications. AKS is a popular choice for running containers in production because it provides built-in load balancing, scaling, and monitoring capabilities. AKS allows you to deploy and manage your containers using Kubernetes, which is an open-source container orchestration system that has become the de facto standard for container management. AKS is cost-effective and requires minimal maintenance overhead, making it an excellent choice for this scenario.
D. Azure Container Instances: Azure Container Instances (ACI) is a serverless container solution that allows you to run containers without having to manage any infrastructure. ACI is a good choice if you need to run a single container or if you need to run containers on demand. However, ACI may not be the best option for this scenario, where you need to deploy two containers as a group.
In summary, based on the requirements of the scenario, the best option is to use Azure Kubernetes Service (AKS). AKS provides a cost-effective and easy-to-manage way to deploy and manage containers, making it an ideal choice for this scenario.