Google Kubernetes Engine vs. TeamCity

If your application is complex, if it's planet-scale, or if you need autoscaling, then Kubernetes is best suited. If your application is straightforward, you can opt for App Engine or Cloud Run. In many cases, you can prefer to run the cloud on GKE. But once you deploy on Kubernetes, you get the flexibility to try different things. But if you don't seek flexibility, it's not an option for you.

Incentivized

TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.

Incentivized

• Engine upgrade rollout strategy - well documented and configurable
• Integration with other Google Cloud services like the Compute Engine, SaaS databases, and some cloud networking like Cloud Armor
• Graphical interface for a lot of operations - either for a quick peek/overview or actual work done by administrators and/or developers (via the Google Cloud Console, for example)

Incentivized

• TeamCity provides a great integration with git, especially Bitbucket.
• When a new code release (build) fails TeamCity has a great tool for investigation and troubleshooting.
• TeamCity provides a user-friendly interface. While some technical knowledge is required to use TeamCity, the design helps simply things.

Incentivized

• Support of IPv6.
• Better GitOps.
• A "serverless" Kubernetes so we can install Google config connector will be really awesome.
• Container-native load balancers do not support internal TCP/UDP load balancers or network load balancers.

Incentivized

• The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
• Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.

Incentivized

• Google Kubernetes Engine has a good UI and documentation that facilitates setup and helps get projects moving along quickly
• Its built-in logging integrations with StackDriver make it easier to monitor the application and log issues quickly
• Automated orchestration, deployment, and scaling of nodes and networking are all easily configurable with yaml files

Incentivized

TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.

Incentivized

Very good Kubernetes distribution with a reasonable total price. Integration with storage and load balancer for ingress and services speed up every process deployment.

Incentivized

GKE spins up new nodes a LOT faster than AKS. GKE's auto scaler runs a lot smoother than AKS. GKE has a lot more Kubernetes features baked in natively.

Incentivized

TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.

Incentivized

• When issues came up, we reached out to some folks at GCP and they seemed to be very prompt and attentive to our needs. They were always willing to help and provide additional details or recommendations or links to resources. This kind of support is very helpful as it allows us to navigate GKE with more confidence.

Incentivized

• Reduced cloud computing costs.
• Easier management of applications.
• Extra time investment to learn how to setup applications in Google versus Amazon.

Incentivized

• TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
• TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
• TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.

Incentivized