IT Specialist | SRE | Cloud Public and Private at Parana Banco
Real User
Top 5
Sep 16, 2025
I use the product for the environments in the company, specifically for the environments in production, QA, and development. I used it in the finance industry at a bank. Now I have moved to another bank, which is the biggest.
We are a customer from a government organization. The solution is used for products related to machine learning. Since we are a government organization, we do not see any profit.
My primary use case is building and deploying solutions using multiple Azure services. I combine these services to build systems on Azure Kubernetes Service (AKS). Since I work mainly as a back-end developer, my focus is on deploying these solutions within AKS environments.
Enterprise Architect at a mining and metals company with 10,001+ employees
Real User
Top 5
Sep 13, 2024
I am using Azure Kubernetes Service (AKS) for enterprise applications. These applications are divided into microservices, and we have multiple environments hosting various applications within Kubernetes.
Principal Cloud Architect at a wholesaler/distributor with 1,001-5,000 employees
Real User
Top 10
Sep 12, 2024
We use the product mostly for development purposes. Some are in the pilot phase for customer usage, however, there's no real production workload active right now on these services. It is mostly for dev test and pilot purposes.
Learn what your peers think about Azure Kubernetes Service (AKS). Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
The solution is used to deploy applications in a very highly scalable model. Any customer can deploy the application. They won't have to worry about the scalability and reliability of the VM. Most things are taken care of by AKS.
Our primary use case for Azure Kubernetes Service (AKS) is containerizing and deploying microservices applications for high scalability within our environment.
Principal Data Engineer at a tech services company with 11-50 employees
Real User
Top 5
Oct 2, 2023
AKS is an orchestrator for containers you can manage within the Azure environment. It is the equivalent of AWS' EKS, and Google Cloud's equivalent is Kubernetes native service. AKS' main feature is that it helps you fetch, scale, and manage containers living within any sort of eco-space within Azure or other platforms to run them on demand. It provisions and scales containers on demand based on your configuration.
Director, Digital Strategy and Architecture at a consultancy with 10,001+ employees
Real User
Jul 14, 2023
Our use case is for any microservice that requires a Kubernetes platform for deployment. But primarily, my reason for using it was to develop a tool for our clients to migrate their deployments from Pivotal Cloud Foundry, which is now out of support. I wrote a tool to automatically convert Pivotal configurations into Kubernetes and then deployed them on Azure Kubernetes Service for testing the mapping and tool output. So it's more of a migration from Pivotal Cloud Foundry to Kubernetes and deployments, with Azure AKS as the target platform.
We began utilizing AKS this year. Our aim is to embrace cloud-native practices, and Kubernetes is an excellent choice for achieving that. Additionally, Nicola seems to be well-suited for our needs. Therefore, we decided to adopt Kubernetes as our platform for software development. This allows us to enable the app team to effortlessly create infrastructure using the infrastructure scope. While we still rely on virtual machines, it is solely for the purpose of visualization, not for hosting the service. Our focus remains on building specialized software.
Solutions Architect at a tech services company with 51-200 employees
Real User
Jan 27, 2023
We use this solution to create multiple clusters and multiple services then scale them, as well as to build network security services around our containers.
Our primary use case is to host our applications for Azure Cloud, rather than hosting the application on our on-premises infrastructure. We are hosting our applications in Kubernetes in Azure Cloud. I work for a product waste company, central components wherein during the weekend the traffic is more and during the weekdays the traffic is less. During festival time, the web traffic is more. So we need some kind of automatic solution. When the web traffic is more, the Kubernetes Service auto-scales, increasing the number of resources like horizontal scaling or vertical scaling. And if the web traffic is less, it descales, like releasing some of the resources. Kubernetes helps in autoscaling and that is why we migrated from on-premises to Kubernetes.
Azure Kubernetes Service (AKS) is a fully managed container orchestration service provided by Microsoft Azure. It simplifies the deployment, management, and scaling of containerized applications using Kubernetes. With AKS, developers can focus on building applications while Azure takes care of the underlying infrastructure. It offers features like automatic scaling, monitoring, and security, ensuring high availability and reliability. AKS integrates seamlessly with other Azure services,...
I use the product for the environments in the company, specifically for the environments in production, QA, and development. I used it in the finance industry at a bank. Now I have moved to another bank, which is the biggest.
Could you please describe your customers' usual use cases for Azure Kubernetes Service (AKS)?
We are a customer from a government organization. The solution is used for products related to machine learning. Since we are a government organization, we do not see any profit.
My primary use case is building and deploying solutions using multiple Azure services. I combine these services to build systems on Azure Kubernetes Service (AKS). Since I work mainly as a back-end developer, my focus is on deploying these solutions within AKS environments.
I am using Azure Kubernetes Service (AKS) for enterprise applications. These applications are divided into microservices, and we have multiple environments hosting various applications within Kubernetes.
We use the product mostly for development purposes. Some are in the pilot phase for customer usage, however, there's no real production workload active right now on these services. It is mostly for dev test and pilot purposes.
I use the solution for micro-services deployment. Azure Kubernetes Service (AKS) has helped reduce downtime.
The solution is used to deploy applications in a very highly scalable model. Any customer can deploy the application. They won't have to worry about the scalability and reliability of the VM. Most things are taken care of by AKS.
Our primary use case for Azure Kubernetes Service (AKS) is containerizing and deploying microservices applications for high scalability within our environment.
AKS is an orchestrator for containers you can manage within the Azure environment. It is the equivalent of AWS' EKS, and Google Cloud's equivalent is Kubernetes native service. AKS' main feature is that it helps you fetch, scale, and manage containers living within any sort of eco-space within Azure or other platforms to run them on demand. It provisions and scales containers on demand based on your configuration.
It is a hosting platform for creating web applications and deploying them.
We use the platform to host various solutions.
We use AKS for cloud-native migrations.
Our use case is for any microservice that requires a Kubernetes platform for deployment. But primarily, my reason for using it was to develop a tool for our clients to migrate their deployments from Pivotal Cloud Foundry, which is now out of support. I wrote a tool to automatically convert Pivotal configurations into Kubernetes and then deployed them on Azure Kubernetes Service for testing the mapping and tool output. So it's more of a migration from Pivotal Cloud Foundry to Kubernetes and deployments, with Azure AKS as the target platform.
I use the solution for infrastructure services on platforms. It can be used for running virtual instances on Azure.
We began utilizing AKS this year. Our aim is to embrace cloud-native practices, and Kubernetes is an excellent choice for achieving that. Additionally, Nicola seems to be well-suited for our needs. Therefore, we decided to adopt Kubernetes as our platform for software development. This allows us to enable the app team to effortlessly create infrastructure using the infrastructure scope. While we still rely on virtual machines, it is solely for the purpose of visualization, not for hosting the service. Our focus remains on building specialized software.
We use the solution to deploy and manage containerized applications.
We need Kubernetes to manage some applications and containers. We use this product as an organizational service.
The AKS service is used as container orchestration for a product based on microservice architecture and as computing layer abstraction.
We use this solution to create multiple clusters and multiple services then scale them, as well as to build network security services around our containers.
Our primary use case is to host our applications for Azure Cloud, rather than hosting the application on our on-premises infrastructure. We are hosting our applications in Kubernetes in Azure Cloud. I work for a product waste company, central components wherein during the weekend the traffic is more and during the weekdays the traffic is less. During festival time, the web traffic is more. So we need some kind of automatic solution. When the web traffic is more, the Kubernetes Service auto-scales, increasing the number of resources like horizontal scaling or vertical scaling. And if the web traffic is less, it descales, like releasing some of the resources. Kubernetes helps in autoscaling and that is why we migrated from on-premises to Kubernetes.
Our primary use case is for deploying the Docker images, which we are working on.
All our microservices are deployed with Azure Kubernetes Service.