Azure Kubernetes Service (AKS) vs. Cisco Hybrid Solution for Kubernetes on AWS

At one instance, there was a fire in our data center and the backup power had some issues because of which the whole DC went down. I believe with AKS and the replication it's easier to handle such a situation. Also, the scenario would have been pretty transparent to the end-users.

Incentivized

• Highly repeatable process
• Minimizes the amount of software to install
• Easily scale resources to meet demand

Incentivized

• Need to update cluster manually
• Policies cannot be updated for existing components
• if any change in policy every has to create cluster

Incentivized

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

Incentivized

The ability to create new instances (i.e. elastic provisioning) is probably the fastest with Azure Kubernetes Service compared to the alternatives that I have looked at. From a pricing perspective, Microsoft always seems to find a way to be more competitive in this area, and literally every other field they play in.

Incentivized

• Positive impact in moving applications to cloud from the in-hose data center to save cost
• Sometimes got affected with some bugs on the AKS infrastructure but hasn't caused a big kios as our production footprint in AKS is not yet high

Incentivized