Kubernetes vs. Visual Studio App Center

K8s should be avoided - If your application works well without being converted into microservices-based architecture & fits correctly in a VM, needs less scaling, have a fixed traffic pattern then it is better to keep away from Kubernetes. Otherwise, the operational challenges & technical expertise will add a lot to the OPEX. Also, if you're the one who thinks that containers consume fewer resources as compared to VMs then this is not true. As soon as you convert your application to a microservice-based architecture, a lot of components will add up, shooting your resource consumption even higher than VMs so, please beware. Kubernetes is a good choice - When the application needs quick scaling, is already in microservice-based architecture, has no fixed traffic pattern, most of the employees already have desired skills.

Incentivized

Honestly, it's an all around solution that needs some enhancements. Need to build an app, check! Need to test that app, check! Need to debug that app, check! Visual Studio App Center is a well rounded platform for multiple types of builds and services.

Incentivized

• Complex cluster management can be done with simple commands with strong authentication and authorization schemes
• Exhaustive documentation and open community smoothens the learning process
• As a user a few concepts like pod, deployment and service are sufficient to go a long way

Incentivized

• It supplies the right native integration for test cases both IOS and Android
• Constant device updates means you are working with the right builds to support product use cases
• Excels in automated test cases that are easy to implement, monitor, and digest results

Incentivized

• Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
• The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
• Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.

Incentivized

• Webview support was lacking
• User management seems a bit disconnected from the standard Microsoft ecosystem. Almost feels like you are managing local users and sharing access more than an enterprise solution
• Price could be better
• Buggy on some of the latest versions of windows

Incentivized

Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.

Incentivized

The biggest benefit is in integrations and plug-ins, as well as the fact that it's not open source. I know open source is popular, but we have all been on the downside of open source and waiting for things to be voted up or a contribution to fix an issue. This alone makes VSAC a nice solution! Plus, it comes with a complete IDE integration of services, documentation, and is light weight

Incentivized

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Incentivized

• Cut down on time to delivery enhancements and overall builds to users
• Helps test new proposed releases with ease
• Cuts down on local build issues as it does do a good job with local development environments as well

Incentivized