The Mirantis Kubernetes Engine (formerly Docker Enterprise, acquired by Mirantis in November 2019)aims to let users ship code faster. Mirantis Kubernetes Engine gives users one set of APIs and tools to deploy, manage, and observe secure-by-default, certified, batteries-included Kubernetes clusters on any infrastructure: public cloud, private cloud, or bare metal.
$500
per year per node
TeamCity
Score 7.3 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
N/A
Pricing
Mirantis Kubernetes Engine
TeamCity
Editions & Modules
Free
$0.00
per year
Basic
$500.00
per year
No answers on this topic
Offerings
Pricing Offerings
Mirantis Kubernetes Engine
TeamCity
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
These pricing options are compatible with Linux or Windows Server and are per year, per node. The basic version requires maximum online purchase not to exceed 50 nodes. Support/professional services are not included.
—
More Pricing Information
Community Pulse
Mirantis Kubernetes Engine
TeamCity
Considered Both Products
Mirantis Kubernetes Engine
Verified User
Engineer
Chose Mirantis Kubernetes Engine
I would also compare to BSD Jails, LXC, and Solaris Zones, but they weren't listed. One of the first reasons we decided to use Docker over other container applications is because Docker is the default everyone recommends and is easily the most popular. We found Docker to be …
Prior to docker, we had a custom build and deployment system. For local development, we use VirtualBox to host our VMs, while our custom VMs resided directly on the servers. We chose Docker primarily to allow us to get rid of our custom deployment system, both simplifying build …
[Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs and separates any single application from the dependencies. Also, this tool is helping me in the agile development of the processes. It is strongly recommended to almost all major organizations.
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.
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.
Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
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.
The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.
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.
Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams.
Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams
Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization.
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.
