Azure Kubernetes Service (AKS) vs. IBM Cloud Private

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

IBM Cloud Private is an ideal platform for companies to accelerate their business growth. It helps in reducing the cost of IT and operations while delivering a great customer experience. With IBM Cloud Private, you can gain agility and security with a flexible hybrid model that fits your needs. It's highly recommended to my colleagues from me.

Incentivized

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

Incentivized

• Capacity On Demand to scale up and down environments
• SaaS model allows our team to have less involvement in managing or controlling the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities.
• SaaS model allows our team to worry less about upgrades, fix packs, environment support etc.

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

• Bluemix/IBM Cloud UI can be better
• Changing Brand name from Bluemix to IBM Cloud, as we are habituated to Bluemix more

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

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

With VMware cloud, each VMware Cloud customer must have an SDDC account(VMC) as well as a general AWS account. The two accounts must be linked for the service to work which is a tiresome thing to do for some clients but with IBM Cloud Private all these issues are solved.

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

• IBM Cloud has helped us start using the cloud and migrating old services to the cloud.

Incentivized