Overall Satisfaction with Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS) is being used primarily to support internal analytics applications that need to scale up and down for a variable user base each day. These internal applications support warehouse operations primarily but we are branching out to other functions such as sales, product development and marketing science.
- Scales quickly when the user base increases randomly
- Downgrades very fast if a bunch of users hop off the system
- Great dev UX for IT
- The pricing structure is complicated
- The stats on usage isn't the easiest to understand
- The overall microsoft contract is hard to wrap my head around
- Only paying for storage we use
- Awesome documentation process
- Dev UX is pretty solid
- The ability to scale has reduced the need for headcount in IT
- The authentication process has kept us compliant with regulatory bodies
- The ability to replicate environments is great.
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.
Do you think Azure Kubernetes Service (AKS) delivers good value for the price?
Are you happy with Azure Kubernetes Service (AKS)'s feature set?
Did Azure Kubernetes Service (AKS) live up to sales and marketing promises?
Did implementation of Azure Kubernetes Service (AKS) go as expected?
Would you buy Azure Kubernetes Service (AKS) again?
Azure Kubernetes Service is well suited for companies that need to rapidly scale (or remove storage capacity) quickly to support any type of online application. In our case, we built an application for the warehouse team. Around the holidays, when the staff increases quickly, the applications have way more users, requiring more storage.