Kubernetes vs. Mirantis Kubernetes Engine

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Kubernetes
Score 8.9 out of 10
N/A
Kubernetes is an open-source container cluster manager.N/A
Mirantis Kubernetes Engine
Score 9.4 out of 10
N/A
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
Pricing
KubernetesMirantis Kubernetes Engine
Editions & Modules
No answers on this topic
Free
$0.00
per year
Basic
$500.00
per year
Offerings
Pricing Offerings
KubernetesMirantis Kubernetes Engine
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional DetailsThese 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
KubernetesMirantis Kubernetes Engine
Considered Both Products
Kubernetes
Chose Kubernetes
Kubernetes is a great alternative to cloud hosted expensive solutions. It is extremely well documented and maintained. It is probably the best home-grown solution available for container infrastructure management.
Chose Kubernetes
Kubernetes is very unique. I do not think there are any competitors to take over its leading place. And you can always use Kuberntes with other tools to make the whole system better. Kubernetes is backed up by Google and has been tested over the years. It is reliable, fast, and …
Chose Kubernetes
When planning our latest product we tried out many hosted container service and a few local tools. These included services run by Google, Microsoft, and Amazon and tools from companies like Docker and Apache. We ended up selecting Kubernetes because it was compatible with all …
Chose Kubernetes
Docker Swarm is not as advanced as Kubernetes and there are no out of the box solutions for auto scaling and deployment strategies. Docker swarm doesnot have much experience with production deployments at scale. Swarm has a smaller community, and less frequent releases as …
Chose Kubernetes
We already had an enterprise Kubernetes 8 set up, so once we got our namespace it took me about 2 weeks to go from not knowing anything to having a self-contained jar in a container, running on Kubernetes 8. In comparison, it took me two weeks to install Java on a blank server …
Mirantis Kubernetes Engine
Chose Mirantis Kubernetes Engine
Docker isn’t a buzz word. It has promising return on investment and a bright future ahead backed up by the open source community.
Chose Mirantis Kubernetes Engine
While Ansible and Docker focus on solving two different problems, we were previously using Ansible to ensure that all dependencies were automatically setup on new servers and that proper configuration was applied when new nodes were brought up. With docker, most of these …
Chose Mirantis Kubernetes Engine
Doocker lacks a lot of the scaling, automation, integration of 3rd party tools/solutions, and integration of shared high-performance self-healing storage, solutions like Heketi provide those missing pieces.
Chose Mirantis Kubernetes Engine
Docker is a different beast in that it is not trying to solve all of your infrastructure problems or most of them, it is simply trying to provide a reliable container serviced based on linux containers in which you can easily and quickly deploy microservices. LXD does provide …
Chose Mirantis Kubernetes Engine
Before Docker, we were using Chef to manage our deployments. Chef didn't provide the environmental consistency and release confidence we needed. We had a split process between how the build servers, the developers and the deployed environments were managing the software …
Chose Mirantis Kubernetes Engine
LXC is great tool if you do not want to deal with any learning curve, however, we found a huge stumbling block when it comes down to having to port the newly created container throughout the company's serves and machines. With Docker everything is smooth, as all we needed was …
Top Pros
Top Cons
Features
KubernetesMirantis Kubernetes Engine
Container Management
Comparison of Container Management features of Product A and Product B
Kubernetes
7.8
1 Ratings
0% above category average
Mirantis Kubernetes Engine
-
Ratings
Security and Isolation10.01 Ratings00 Ratings
Container Orchestration7.01 Ratings00 Ratings
Cluster Management9.01 Ratings00 Ratings
Storage Management9.01 Ratings00 Ratings
Resource Allocation and Optimization8.01 Ratings00 Ratings
Discovery Tools5.01 Ratings00 Ratings
Update Rollouts and Rollbacks5.01 Ratings00 Ratings
Analytics, Monitoring, and Logging9.01 Ratings00 Ratings
Best Alternatives
KubernetesMirantis Kubernetes Engine
Small Businesses
Portainer
Portainer
Score 9.4 out of 10
Portainer
Portainer
Score 9.4 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.2 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
KubernetesMirantis Kubernetes Engine
Likelihood to Recommend
9.0
(16 ratings)
8.3
(37 ratings)
Likelihood to Renew
-
(0 ratings)
9.1
(1 ratings)
Usability
-
(0 ratings)
8.0
(2 ratings)
Support Rating
-
(0 ratings)
7.8
(3 ratings)
User Testimonials
KubernetesMirantis Kubernetes Engine
Likelihood to Recommend
Kubernetes
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.
Read full review
Mirantis
[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.
Read full review
Pros
Kubernetes
  • 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
Read full review
Mirantis
  • Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux
  • Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server
  • CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up.
Read full review
Cons
Kubernetes
  • 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.
Read full review
Mirantis
  • Containers are often opaque - if a container doesn't work out of the box, it's messy to fix.
  • Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be.
  • Networking is complexified due to internal port mapping between containers, etc.
Read full review
Usability
Kubernetes
No answers on this topic
Mirantis
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.
Read full review
Support Rating
Kubernetes
No answers on this topic
Mirantis
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.
Read full review
Alternatives Considered
Kubernetes
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.
Read full review
Mirantis
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.
Read full review
Return on Investment
Kubernetes
  • 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.
Read full review
Mirantis
  • 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.
Read full review
ScreenShots