Azure Container Apps vs. Azure Kubernetes Service (AKS)

Azure Container Apps is a welcome addition for sure. Based on my experience, this has enabled us to move fully to the cloud and managed everywhere in one spot and on the go. We can scale it to our end as much as we would like. It can be assess anywhere and it is fully secure

Incentivized

AKS works very well for running containerized applications that require high availability and scalability. This includes systems like our HRIS platform and customer-facing web applications. AKS is a good choice when applications are broken into multiple services that need independent scaling and deployment. It provides the flexibility needed to manage these architectures effectively. But for single, low-traffic applications or simple internal tools, AKS can be overkill. For scenarios like that Azure App Service would be better.

Incentivized

• Gives user a level of autonomous access
• No control plane or node pool to manage
• Less kubernetes experience required
• Easily integrate with Azure devops

Incentivized

• AKS makes it easier to replicate data to multiple regions
• Azure portal make it easier to manage the resources of the organization

Incentivized

• Continue to enhance security
• Better pricing
• Flexibility

Incentivized

• Steep learning curve
• Expected charges are unclear until you see real production usage
• Operations teams need to learn an entirely new skill set

Incentivized

I would rather use AKS for my critical applications. The fact that the deployment process is dependent on as cli makes it hard for us to integrate with our standard CI/CD tools

Incentivized

Azure Container Apps are fantastic and it is a game changer. I would recommend it to anyone considering it. As you can scale it to what you would like and it is fully cloud native with better security. It is a no brainier not to consider it. I do believe that with further improve it will become even more attractive

Incentivized

As already said, the UI/CLI and even terraform are perfectly fine, but certain details could be documented better. For instance, if I want to secure the whole Azure Kubernetes Service (AKS) with my own managed keys, then it is very complex and hard to get there. Not really a single source that gives you the whole picture. Besides that, it is still good to use, in most cases intuitive but details mentioned as above can be tricky.

Incentivized

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

Incentivized

Amazon EKS stacked up very well and had better performance in some areas. However, Azure Kubernetes Service was a better fit given our Azure environment.

Incentivized

• As it is cloud native, we no longer required to have onsite prem
• Reducing both from an energy and security perspective
• It is worth the investment as we have saved about 10% of our ICT cost

Incentivized

• We had to spend more time on Azure Kubernetes Service (AKS) than on AWS and GCP to get our kubernetes cluster up and running
• The resources on nodes need to be left out unused, so effectively it is wasting money there
• It definitely made us spend more time into maintaining kubernetes

Incentivized